"Didn't find RecordId in WiredTigerRecordStore" on collections after an idle period

A bug in an internal WiredTiger thread could cause corruption in collections that become idle, then are later updated again.

A WiredTiger thread that discards old collections in cache could (under rare circumstances) start discarding a collection but give up part way through, leaving an incomplete tree in cache. If that collection was subsequently updated, the on-disk tree could become corrupted. A repairDatabase operation may be required to salvage data.