As part of SERVER-72229 we made setFCV implement an "upgrade" step that scrubbed encryption options from all local WT collections. This was further reinforced by SERVER-79496 to ban using the options on new nodes but had to be wrapped in a feature flag as part of SERVER-82203.

However, this was done without taking into consideration concurrent DDL operations. As such the collection could be created with encryption options during FCV upgrade by a DDL coordinator and missed by the FCV upgrade step. That is, the set of collections we scrub the option from might not be complete.

This also conflicts with sharding DDL operations since the collMod occurs locally without taking any sharding DDL locks.