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.
}
    // Make th
    context.chain->initMessage(_("Loading …").translated);
    stdshared_ptr<CWallet>  = CWalletCreate(context, name, stdmove(database), _creation_flags, error, warnings);
    if (!) {
        error = Untranslated("Wallet creation failed.") + Untranslated(" ") + error;
        status = DatabaseStatusFAILED_CREATE;
        return nullptr;
    }
    // E
    if (!passphrempty() && !(_creation_flags & WALLET_FLAG_DISABLE_PRIVATE_KEYS)) {
        if (!->EncryptWallet(passphrase)) {
            error = Untranslated("Error Wallet created but failed to encrypt.");
            status = DatabaseStatusFAILED_ENCRYPT;
            return nullptr;
        }
        if (!create_blank) {
            // U
            if (!->Unlock(passphrase)) {
                error = Untranslated("Error Wallet was encrypted but could not be unlocked");
                status = DatabaseStatusFAILED_ENCRYPT;
                return nullptr;
            }
            // S
            {
                LOCK(->cs_);
                if (->IsWalletFlagSet(WALLET_FLAG_DESCRIPTORS)) {
                    ->SetupDescriptorScriptPubKeyMans();
                } else {
                    for (auto spk_man  ->GetActiveScriptPubKeyMans()) {