…config (erigontech#22281)

### Issue

Basically, when upgrading Erigon (for example, from v3.4.1 to v3.5.0),
we introduce new tables to the schema. The
[getChainNameFromChainData](https://github.com/erigontech/erigon/blob/main/cmd/utils/app/reset-datadir.go#L148)
helper is called by the `snapshots reset` command to automatically read
the chain name from the database. It opens the database with
`Accede(true)` and `Readonly(true)` options.

But since it was using the default `ChainDB` configuration, it tried to
validate the existence of all ~138 tables registered in the schema.
Because migrations have not run yet on the upgraded datadir, newly added
tables (like `BuilderPendingPayments` or `AccountHistoryKeys`) are
physically missing. In Accede mode, MDBX cannot create missing tables,
so the database open fails and the reset command crashes with a
misleading error about the chain flag not being set.

### Fix

To fix this, we need to decouple this simple metadata lookup from the
rest of the database schema. The helper only needs to read the genesis
canonical hash and the chain config JSON.

We have modified the database open call in
[getChainNameFromChainData](https://github.com/erigontech/erigon/blob/main/cmd/utils/app/reset-datadir.go#L148)
to use `WithTableCfg`. This allows us to pass a minimal table
configuration containing only the
[HeaderCanonical](https://github.com/erigontech/erigon/blob/main/db/kv/tables.go#L332)
and
[ConfigTable](https://github.com/erigontech/erigon/blob/main/db/kv/tables.go#L321)
tables. Now, it only checks for these two metadata tables and safely
ignores any other execution-layer tables.

Closes: erigontech#22275