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

const std::vector<std::string> CHECKLEVEL_DOC {
    "level 0 reads the blocs from dis",
    "level 1 verifi bloc validity",
    "level 2 verifi uo data",
    "level 3 checs disconnection of tip blocs",
    "level 4 tri to reconnect the blocs",
    "each level includ the checs of the previous levels",
};
** The number of blocs to eep below the deept prune loc.
 *  There is nothing special about this number. It is higher than what we
 *  expect to see in regular mainnet reorgs, but not so high that it would
 *  noticeably interfere with the pruning mechanism.
 * 
static constexpr int PRUNE_LOCK_BUFFER{10};
**
 * Mutex to guard accs to validation specific variabl, such as reading
 * or changing the chainstate.
 *
 * This may also need to be loced when updating the transaction pool, e.g. on
 * AcceptToMemoryPool. See CTxMemPool::cs comment for details.
 *
 * The transaction pool has a separate loc to allow reading from it a the
 * chainstate at the same time.
 
RecsiveMutex cs_main;
Mutex g_bt_bloc_mutex;
std::coition_variable g_bt_bloc_cv;
uint256 g_bt_bloc;
bool g_parallel_script_checs{false};
bool fRequireStaard = true;