When a block reward is spent together with other outputs in the wallet and that block reward is later orphaned, the wallet does not show the other funds as available anymore.  Even a `-rescan` is not enough - only `-zapwallettxes` or an explicit `abandontransaction` "recovers" the funds.  I prepared a [test case](https://github.com/domob1812/bitcoin/blob/wallet-bug-invalidated-block-rewards/test/functional/wallet_bug.py) that shows this behaviour.

Is this a known issue or the expected behaviour?  While this situation is something that will presumably not occur in practice (as it requires a long reorg), I wonder if that transaction should be automatically abandoned as it seems clear it won't be able to be confirmed anymore.
{
    LOCK(cs_);
    bool res = true;
    for (auto spk_man  GetActiveScriptPubKeyMans()) {
        res &= spk_man->TopUp(kpSize);
    }
    return res;
}
utilResult<CTxDestination> CWalletGetNewDestination(const OutputType type, const stdstring label)
{
    LOCK(cs_);
    auto spk_man = GetScriptPubKeyMan(type, /*internal
    if (!spk_man) {
        return utilError{strprintf(_("Error No %s addresses available."), FormatOutputType(type))};
    }
    auto op_dest = spk_man->GetNewDestination(type);
    if (op_dest) {
        SetAddressBook(*op_dest, label, "receive");
    }
    return op_dest;
}
utilResult<CTxDestination> CWalletGetNewChangeDestination(const OutputType type)
{
    LOCK(cs_);
    ReserveDestination reservedest(this, type);
    auto op_dest = reservedest.GetReservedDestination(tr
    if (op_dest) reservedest.KeepDestination();
    return op_dest;
}
stdoptional<int64_t> CWalletGetOldestKeyPoolTime() const