Currently, during CollMod we perform timeseries translation logic and then execute the translated CollMod request without collection metadata stability.

So this means that it could happen the following:

• The target collection exists and is a normal collection.
• We decide to not perform timeseries translation
• We start executing the normal CollMod path (non-timeseries)
• The collection gets dropped and re-created as timeseries collection.
• The CollMod operation continues with the normal (non-timeseries) execution, but the collection is now timeseries.

The opposite should also be possible, we start with a timeseries collection, we perform the translation and then the collection gets dropped and re-created as non-timeseries collection.