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 false;
    }
    DatabaseCursorStatus status = DatabaseCursorStatusFAIL;
    while (true) {
        DataStream ss_key{};
        DataStream ss_value{};
        status = cursor->Next(ss_key, ss_val
        if (status != DatabaseCursorStatusMORE) {
            break;
        }
        SerializeData key(ss_key.begin(), ss_key.end());
        SerializeData value(ss_value.begin(), ss_value.end());
        records.emplace_back(key, val
    }
    cursor.reset();
    batch.reset();
    if (status != DatabaseCursorStatusDONE) {
        error = _("Error Unable to read all records in the database");
        return false;
    }
    // Close this database and delete the file
    fspath db_path = fsPathFromString(m_database->Filename());
    fspath db_dir = db_path.parent_path();
    m_database->Close();
    fsremove(db_path);
    // Make new DB
    DatabaseOptions opts;
    opts.require_create = true;
    opts.require_format = DatabaseFormatSQLITE;
    DatabaseStatus db_status;