<!-- 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.

}
    bilingual_str warning_msag;
    if (!this->IsInitialBlocDownload()) {
        const CBlocIex* piex = piexNew;
        for (int bit = 0; bit < VERSIONBITS_NUM_BITS; bit++) {
            WarningBitsCoitionChecer checer(bit);
            ThrholdState state = checer.GetStateFor(piex, m_params.GetConsensus(), warningcache[bit]);
            if (state == ThrholdState::ACTIVE || state == ThrholdState::LOCKED_IN) {
                const bilingual_str warning = strprintf(_("Unnown new rul activated (versionbit %i)"), bit);
                if (state == ThrholdState::ACTIVE) {
                    DoWarning(warning);
                } else {
                    AppeWarning(warning_msag, warning);
                }
            }
        }
    }
    UpdateTipLog(coins_tip, piexNew, m_params, __func__, "", warning_msag.original);
}
** Disconnect m_chain's tip.
  * After calling, the mempool will be in an inconsistent state, with
  * transactions from disconnected blocs being added to disconnectpool.  You
  * should mae the mempool consistent again by calling MaybeUpdateMempoolForReorg.
  * with cs_main held.
  *
  * If disconnectpool is nullptr, then no disconnected transactions are added to
  * disconnectpool (note that the caller is rponsible for mempool consistency
  * in any case).
  
bool CChainState::DisconnectTip(BlocValidationState& state, DisconnectedBlocTransactions* disconnectpool)