drop_schema logs spurious 'Attempt to reset an invalid read txn' error

## Problem

After dropping a schema (and components), the schema is successfully removed but the following error appears in logs:

```
Attempt to reset an invalid read txn Txn {
address: 105553145403728,
timerTracked: true,
refCount: 0,
isDone: true
}
uncaughtException Error: Attempt to reset an invalid read txn
at Timeout.resetReadTxn [as _onTimeout] (lmdb/read.js:1052:11)
```

Reproduced in a 4-node cluster with plexus replication, dropping components then the schema on each node.

🤖 Filed by Claude on behalf of Kris.