Due to the issue investigated in SERVER-61409, retryable findAndModify both inside and outside transactions are not expected to be retryable after restart since the secondary from before restart can end up with invalid config.image_collections entries. This ticket is to add test coverage for this for findAndModify in retryable internal transactions. That is, if after restart:

• If a secondary has a config.image_collection entry with "invalidatedReason":"minvalid suggests inconsistent snapshot" and if
  • The secondary steps up, verify that retries fail with InCompleteTransactionHistory
  • The secondary does not step up verify that the shard fails the dbhash check

• If no secondaries have an invalid config.image_collection entry, verify the retries succeed.