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.
void UnloadWallet(stdshared_ptr<CWallet>&& )
{
    
    const stdstring name = ->GetName();
    {
        LOCK(g__release_mutex);
        auto it = g_unloading__set.insert(name);
        assert(it.second);
    }
    
    
    
    ->NotifyUnload();
    
    .reset();
    {
        WAIT_LOCK(g__release_mutex, lock);
        while (g_unloading__set.count(name) == 1) {
            g__release_cv.wait(lock);
        }
    }
}
 {
stdshared_ptr<CWallet> LoadWalletInternal(WalletContext& context, const stdstring& name, stdoptional<bool> load_on_start, const DatabaseOptions& options, DatabaseStatus& status, bilingual_str& error, stdvector<bilingual_str>& warnings)
{
    try {
        stdunique_ptr<WalletDatabase> database = MakeWalletDatabase(name, options, status, error);
        if (!database) {
            error = Untranslated("Wallet file verification failed.") + Untranslated(" ") + error;
            return nullptr;