This has changed the `maxCatchUpPercentageBeforeBlockingWrites` parameter to be settable both at startup (as before) and at runtime (new). We should update the server parameters doc section about this parameter. Here is the link to the doc in question: https://www.mongodb.com/docs/manual/reference/parameters/#mongodb-parameter-param.maxCatchUpPercentageBeforeBlockingWrites

We should replace the line:
"You cannot change
maxCatchUpPercentageBeforeBlockingWrites
during runtime."
With:
"During runtime, you can also set the parameter with the setParameter command:

db.adminCommand(

{ setParameter: 1, maxCatchUpPercentageBeforeBlockingWrites: 20}

)"

Similar to the last two sentences in this section: https://www.mongodb.com/docs/manual/reference/parameters/#mongodb-parameter-param.enableShardedIndexConsistencyCheck.
Though we should specify that this is only settable at runtime from 7.1.

Description of Linked Ticket

The test (which performs concurrent user writes an chunk migrations)is currently blacklisted from config fuzzer passthrough suites because it is sensitive to specific values of a threshold parameter (details described here).

In order to re-enable it, we can either tolerate timeout errors or exclude the execution of migration when the server parameter regulating the migration goes below a threshold value (to be qualified).