[sys-4815] consistency check when replicating epoch number

[seckcoder]

Main changes:

• Fixed one minor issue found when upgrading rocksdb. It's possible for epoch number to be diverged between leader and follower. This can happen when we do epoch recovery during db open (i.e., nodes run with different rocksdb versions and nodes upgrading from old version to new version need to recover epoch. Epoch number of nodes which do epoch recovery might go backwards, causing divergence of epoch number). Instead of treating it as corruption, we can simply poison the follower shard and reopen it. More details: https://linear.app/rockset/issue/SYS-4815#comment-94888521
• Added more checks when replicating epoch number between leader follower. 1) check that next_epoch_number on follower is correct. This is important to guarantee that epoch number doesn't go backwards after all nodes are on new version. 2) check that replicated epoch number = epoch number inferred on follower.

TESTS

• extended the stress test to cover the code changes

[igorcanadi]

Nice! It might be better to return poison through ApplyReplicationLogRecordInfo to avoid polluting RocksDB codebase, but this is fine too, especially if temporary.