[CBM] Restore loses maxTTL info on 7.2 clusters

Problem

1. Create 7.2 cluster
2. Create bucket + collection with >0 maxTTL
3. Backup cluster
4. Drop the bucket
5. Restore the bucket with --auto-create-buckets
6. The maxTTL of the collection created in step 2 is 0

Fix

This is likely because we disable TTL modification for <7.6 clusters. This is correct for when we're modifying pre-existing collections, but when creating new collections, we should preserve the maxTTL