As part of SERVER-74472 we had to add a new rangeTruncate method that is not tied to the same nuance as the normal truncate method.

In particular, the two differ in the sense that:

• truncate clears out the oplog truncate markers, and clears the sizeStorer info
• rangeTruncate expects the user to provide a hint for how much data it will remove and updates the sizeStorer information only

The difference is subtle, but impedes fully merging the two methods without rewriting the current callers of truncate. Additionally, the Oplog truncate markers would have to be separated from living inside WiredTigerRecordStore in order to align the two methods' behaviour.