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.
return true;
}
bool RemoveWallet(WalletContext& context, const stdshared_ptr<CWallet>& , stdoptional<bool> load_on_start)
{
    stdvector<bilingual_str> warnings;
    return RemoveWallet(context, , load_on_start, warnings);
}
stdvector<stdshared_ptr<CWallet>> GetWallets(WalletContext& context)
{
    LOCK(context.s_mutex);
    return context.s;
}
stdshared_ptr<CWallet> GetDefaultWallet(WalletContext& context, size_t& count)
{
    LOCK(context.s_mutex);
    count = context.s.size();
    return count == 1 ? context.s[0]  nullptr;
}
stdshared_ptr<CWallet> GetWallet(WalletContext& context, const stdstring& name)
{
    LOCK(context.s_mutex);
    for (const stdshared_ptr<CWallet>&   context.s) {
        if (->GetName() == name) return ;
    }
    return nullptr;
}
stdunique_ptr<interfacesHandler> HandleLoadWallet(WalletContext& context, LoadWalletFn load_)
{
    LOCK(context.s_mutex);
    auto it = context._load_fns.emplace(context._load_fns.end(), stdmove(load_));