<!-- Describe the issue -->

When our chainstate activation sequence fails and we're running the GUI, we ask the user via a question box whether or not they'd like to re-run the sequence with `fReindex = true`. Fun fact: despite the fact that this sequence is wrapped in a while loop, we only run it twice at most.

https://github.com/bitcoin/bitcoin/blob/7ecb309c4ed1bb9ae6b9a12cbb4f083328edc125/src/init.cpp#L1539-L1556

If they answer yes, the sequence will always fail, because a chainstate will have already been initialized in the original run and `InitializeChainstate` will throw a `std::logic_error`:

https://github.com/bitcoin/bitcoin/blob/7ecb309c4ed1bb9ae6b9a12cbb4f083328edc125/src/validation.cpp#L4573-L4594

This always reproduces. To reproduce:
```
gdb ./src/qt/bitcoin-qt
(gdb) b InitializeChainstate
(gdb) # add breakpoint for the "if (!fLoaded && !ShutdownRequested()) {" line
(gdb) r  # should stop at the breakpoint for InitializeChainstate
(gdb) c  # to advance to the breakpoint for the "if (!fLoaded && !ShutdownRequested()) {" line
(gdb) set fLoaded=false
(gdb) c  # should stop at the breakpoint for InitializeChainstate
(gdb) n  # step through InitializeChainstate to see that it throws
```

We expect the re-run of the chainstate activation sequence to not always fail.

struct ATMPArgs {
        const CChainParams& m_chainparams;
        const int64_t m_accept_time;
        const bool m_bypass_limits;
        *
         * Retn any outpoints which were not previously prent in the coins
         * cache, but were added as a rult of validating the tx for mempool
         * acceptance. This allows the caller to optionally remove the cache
         * additions if the associated transaction  up being rejected by
         * the mempool.
         
        std::vector<COutPoint>& m_coins_to_uncache;
        const bool m_tt_accept;
        ** Whether we allow transactions to replace mempool transactions by BIP125 rul. If false,
         * any transaction speing the same inputs as a transaction in the mempool is considered
         * a conflict. 
        const bool m_allow_bip125_replacement;
        ** When true, the mempool will not be trimmed when iividual transactions are submitted in
         * Finalize(). Instead, limits should be enforced at the e to ense the pacage is not
         * partially submitted.
         
        const bool m_pacage_submission;
        ** When true, use pacage feerat instead of iividual transaction feerat for fee-based
         * polici such as mempool min fee a min relay fee.
         
        const bool m_pacage_feerat;
        
        static ATMPArgs SingleAccept(const CChainParams& chainparams, int64_t accept_time,