SERVER-91195 provided catalog support to work around the issues described in SERVER-91193 and SERVER-91194. That's an unclean solution meant to target old sub-versions with strict collection options.

We should find a way to properly include those timeseries parameters (and potentially new ones) as normal options. That may be as simple as deciding that both collection options and timeseries options must not be strict anymore.

Once decided how to include such parameters, we must proceed in the following way upon upgrade (as part of setFeatureCompatibilityVersion):

1. Properly set in the new way timeseriesBucketsMayHaveMixedSchemaData (using the machinery implemented under SERVER-84699 to know whether to set or not the option)
2. Properly set in the new way timeseriesBucketingParametersHaveChanged (using the machinery implemented under SERVER-91754  to know whether to set or not the option)
3. Get rid of the old ways to manage such parameters:

• • Top level catalog fields
  • Storage engine fields (SERVER-91195's workaround)