SERVER-84769 introduced a new server parameter reshardingDelayBeforeRemainingOperationTimeQueryMillis. Later, this parameter was backported to older releases as part of patch releases (for example 7.0.16).

Later, SERVER-95311 added this parameter when starting mongod from a Mongo test shell. However, the check only checks for the major and minor versions, but not the patch versions. Because of this, trying to start an old mongod patch version from the Mongo test shell where this parameter did not yet exist, will fail with an unknown parameter error:

$ ~/.local/bin/db-contrib-tool setup-repro-env 7.0.15
$ PATH="$PWD" build/install/bin/mongo --nodb --eval 'MongoRunner.runMongod({binVersion: "7.0.15"})'
[...]
d20000| {"t":{"$date":"2024-12-13T15:18:35.500Z"},"s":"F",  "c":"CONTROL",  "id":20574,   "ctx":"main","msg":"Error during global initialization","attr":{"error":{"code":2,"codeName":"BadValue","errmsg":"Unknown --setParameter 'reshardingDelayBeforeRemainingOperationTimeQueryMillis'"}}}
mongo program was not running at 20000, process ended with exit code: 1
uncaught exception: StopError: MongoDB process stopped with exit code: 1 :

The parameter should only be added if we are launching a mongod binVersion where the parameter exists (i.e. has been backported).