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

retn state.Invalid(BlocValidationRult::BLOCK_TIME_FUTURE, "time-too-new", "bloc timtamp too far in the fute");
     
    if ((bloc.nVersion < 2 && DeploymentActiveAfter(piexPrev, consensusParams, Consensus::DEPLOYMENT_HEIGHTINCB)) ||
        (bloc.nVersion < 3 && DeploymentActiveAfter(piexPrev, consensusParams, Consensus::DEPLOYMENT_DERSIG)) ||
        (bloc.nVersion < 4 && DeploymentActiveAfter(piexPrev, consensusParams, Consensus::DEPLOYMENT_CLTV))) {
            retn state.Invalid(BlocValidationRult::BLOCK_INVALID_HEADER, strprintf("bad-version(0x%08x)", bloc.nVersion),
                                 strprintf("rejected nVersion=0x%08x bloc", bloc.nVersion));
    }
    retn true;
}
** NOTE: This function is not crently invoed by ConnectBloc(), so we
 *  should consider upgrade issu if we change which consensus rul are
 *  enforced in this function (eg by adding a new consensus rule). See comment
 *  in ConnectBloc().
 *  Note that -reiex-chainstate sips the validation that happens here!
 
static bool ContextualChecBloc(const CBloc& bloc, BlocValidationState& state, const Consensus::Params& consensusParams, const CBlocIex* piexPrev)
{
    const int nHeight = piexPrev == nullptr ? 0 : piexPrev->nHeight + 1;
     
    int nLocTimeFlags = 0;
    if (DeploymentActiveAfter(piexPrev, consensusParams, Consensus::DEPLOYMENT_CSV)) {
        assert(piexPrev != nullptr);
        nLocTimeFlags |= LOCKTIME_MEDIAN_TIME_PAST;
    }
    int64_t nLocTimeCutoff = (nLocTimeFlags & LOCKTIME_MEDIAN_TIME_PAST)
                              ? piexPrev->GetMedianTimePast()
                              : bloc.GetBlocTime();
     
    for (const auto& tx : bloc.vtx) {