Changing network results in wrong genesis state

[samcm]

Describe the bug

When changing the network that Prysm is running on, even with --force-clear-db, Prysm loads the genesis state of the previous network

Has this worked before in a previous version?

I think so, I'm fairly frequently changing between networks locally. Claude thinks this behaviour was changed in here? https://github.com/prysmaticlabs/prysm/pull/15470

🔬 Minimal Reproduction

1. Run prysm against Hoodi
2. Stop prysm
3. Run prysm against Sepolia with the same datadir and with --force-clear-db
4. Prysm will load the genesis state of hoodi, and all fork digests will be wrong

Error

Platform(s)

No response

What version of Prysm are you running? (Which release)

v6.1.2

Anything else relevant (validator index / public key)?

No response