Updated Description:
Users should be able to opt out of enforcing replicated recordIds in dbhash equality checks. This will allow users to check data consistency across versions, even if in one version they upgrade to utilize replicatedRecordIds.

Original Description:
We don't want to always use the recordId with dbHash. For example, if a customer has a recordIdsReplicated:false collection and then they upgrade to a repcordIdsReplicated:true collection, because dbHash includes the recordIds when calculating the hash in the latter case, the hash will be different, even if the documents on disk are exactly the same.

This can be confusing for customers if they run dbHash and get value X, upgrade and then get value, they might think that something has gotten corrupted on disk.

So we need to have a flag to make including the recordId opt-in. Likewise for SERVER-86692, the behavior of having dbHash include the natural order should be opt-in via this flag for the same reason. Otherwise someone who upgrades would see that the exact same capped collection was returning a different hash between versions.