stress test fail: Expected State - assertion IsDone failed about speedb HOT 1 OPEN

for the IsDone assertion failure, my findings are:
When the stress test resumes and finds a trace file and state file with a seq number prefix e.g. 0.state ,
The stress test tries to verify the trace file holds all the changes done to the db since that seq number. It does that by replaying the trace file and counting how many put, delete and rangedelete there were. Then it compares that to how many seq numbers have changed since that seq on the file (IsDone assertion).
The assumption that the gap in seq numbers should be equivalent to the number of write and delete operations recorded in the trace file seems very weak to me. The txn db for example doesnt keep those assumptions and it seems like there are other instances where this assumption is false.

since we want to keep the trace file for debugging, for now, the workaround can be that we'll avoid this assertion and only print the numbers (num_write_ops_ and max_write_ops_) for future debugging.

workaround will be done in - #816

from speedb.