This ticket is to track the idemponecy failures we found in BF's after reducing the initial sync attempts to 1 in SERVER-31093.
Recreating collection with different collation during collection cloning phase can causes initial sync attempt to fail
idempotence violation when intermediate document exceeds size threshold
Initial sync should ignore multiple text indexes on same collection error
Ambiguous field name error should be ignored during initial sync
A sequence of rename and create collections that do not arrive at the correct end state
Run listIndexes with a single snapshot during initial sync
Increase initial sync attempts in initial sync passthrough
Restart initial sync for known index idempotency errors; fail for unknown ones.