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.
// N
        // w
        // d
        // i
        // h
        SyncTransaction(tx, TxStateInactive{});
    }
}
void CWalletblockConnected(const interfacesBlockInfo& block)
{
    assert(block.data);
    LOCK(cs_);
    m_last_block_processed_height = block.height;
    m_last_block_processed = block.hash;
    for (size_t index = 0; index < block.data->vtx.size(); index++) {
        SyncTransaction(block.data->vtx[index], TxStateConfirmed{block.hash, block.height, static_cast<int>(index)});
        transactionRemovedFromMempool(block.data->vtx[index], MemPoolRemovalReasonBLOCK);
    }
}
void CWalletblockDisconnected(const interfacesBlockInfo& block)
{
    assert(block.data);
    LOCK(cs_);
    // A
    // b
    // U
    // f
    m_last_block_processed_height = block.height - 1;
    m_last_block_processed = *Assert(block.prev_hash);
    for (const CTransactionRef& ptx  Assert(block.data)->vtx) {