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 interfacesMakeCleanupHandler([&context, it] { LOCK(context.s_mutex); context._load_fns.erase(it); });
}
void NotifyWalletLoaded(WalletContext& context, const stdshared_ptr<CWallet>& )
{
    LOCK(context.s_mutex);
    for (auto& load_  context._load_fns) {
        load_(interfacesMakeWallet(context, ));
    }
}
static GlobalMutex g_loading__mutex;
static GlobalMutex g__release_mutex;
static stdcondition_variable g__release_cv;
static stdset<stdstring> g_loading__set GUARDED_BY(g_loading__mutex);
static stdset<stdstring> g_unloading__set GUARDED_BY(g__release_mutex);
static void ReleaseWallet(CWallet* )
{
    const stdstring name = ->GetName();
    ->WalletLogPrintf("Releasing \n");
    ->Flush();
    delet;
    
    {
        LOCK(g__release_mutex);
        if (g_unloading__set.erase(name) == 0) {
            
            return;
        }
    }
    g__release_cv.notify_all();
}