When renaming a buckets collection across databases, the temporary collection name is created without the system.buckets. prefix.

This can be problematic for several reasons:

• In v8.0/master or v8.2/master multiversion scenarios, oplog application may fails (crash old secondaries) because inserts on non-buckets collections with timeseries options would be interpreted as on viewless timeseries. This leads to generate an oplog entry with the OplogEntryBase.isViewlessTimeseries field.
• In previous versions, checkMetadataConsistency may report the inconsistency (non-buckets collection with TS options)