Under certain conditions in the old protocol, a primary shard can retain a stale dbVersion in its DSS due to previously not being the primary when the version was installed. This leads cloneAuthoritativeMetadata DDL to incorrectly assume the metadata is up-to-date and skip updating it.

While this is harmless in 8.0 FCV, in 9.0 FCV it can cause unavailability due to reliance on shards being authoritative for database metadata.

We need to update cloneAuthoritativeMetadata to correctly detect and handle this case, ensuring the authoritative model is entered with valid, up-to-date database metadata.