RdLrT

Just a note to ensure ghc9* CI builds work prior to dropping ghc8.10, as [per current latest commit](https://github.com/IntersectMBO/cardano-db-sync/actions/runs/12302545920/job/34335638079) - they dont: 

> Unfortunately the GitHub actions are in a pretty bad state right now Afaik - hydra CI is based on nix, the github CI is our only point of reference...

In general would be nice if config settings itself are saved in database, which may be usable to easily verify current runtime config - be it internally for dbsync design/development...

> [@rdlrt](https://github.com/rdlrt) interesting, I like the ideas. We'd have to think of scenarios where configs are changed back and forth by the user and how that might effect snapshots. Also...

> This could still cause minor inconsistencies if the config changes, eg duplucate entries for equivalent configs, however it wouldn't be a huge deal. The idea is to save config...

> I'd like to get input from devs/community before removing things from the release tarball. > ... > cardano-node > cardano-cli > bech32 (useful for decoding addresses) > cardano-ping (soon...

> However I would also like to have versioned links Yes, that is what the issue description (point 2) says 🙂 (`/` - and in addition, `/latest` / `/` )

@disassembler - bumping this , as it hasnt changed a lot (especially wrt `/latest` or `/current` that node team recommends for use on mainnet), which can then be referenced in...

.