Depending on if the current FCV supports the resharding improvements feature flag, resharding will either fill in the simple collation explicitly when making index specs or not (in 8.0 or 7.3). It does this across several feature flag checks, and if FCV changes between checks (between here and here), resharding may pass specs with or without the collation to an index creation path that either requires it for correctness or will reject it with an InternalError response. Either way resharding will fail because FCV changed, so the only user visible impact is resharding may fail with InternalError. This can lead setfcv_aborts_reshard_collection.js to fail in 8.0 and 7.3 (since resharding improvements was enabled in 7.2), and we should update the test to ignore that error, since it already expects resharding to fail.