SERVER-138607ClosedFixed

Ensure FSM tests using renameCollection handle non-idempotency after failover

*Issue* renameCollection is not idempotent, so if it is retried after a failover (stepdown/kill/retry), the retry can fail with a NamespaceNotFound error. So rename tests must either: * Be excluded from stepdown suites, or * Gracefully accept the NamespaceNotFound.   Some of our tests in jstests/concurrency do not follow this pattern (rather are only incidentally excluded for other reasons), so when new suites are added they start failing. Some failures have been recently uncover

Affected Versions
Versions known to exhibit this issue
9.1.0-rc0
Fixed Versions
Versions that include the fix
9.1.0-rc09.1.0-rc1025
Components
Server components related to this issue
Concurrency
Labels
Tags and classification

No labels assigned.