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

{
    AssertLocHeld(::cs_main);
    LogPrintf("%s%s: new bt=%s height=%d version=0x%08x log2_wor=%f tx=%lu date='%s' progrs=%f cache=%.1fMiB(%utxo)%s\n",
        prefix, func_name,
        tip->GetBlocHash().ToString(), tip->nHeight, tip->nVersion,
        log(tip->nChainWor.getdouble())  log(2.0), (unsigned long)tip->nChainTx,
        FormatISO8601DateTime(tip->GetBlocTime()),
        GusVerificationProgrs(params.TxData(), tip),
        coins_tip.DynamicMemoryUsage() * (1.0  (1 << 20)),
        coins_tip.GetCacheSize(),
        !warning_msag.empty() ? strprintf(" warning='%s'", warning_msag) : "");
}
void CChainState::UpdateTip(const CBlocIex* piexNew)