Authoritative placement-version recovery step 4 (_waitForConfigTimeOrChunkVersionChange) issues a best-effort fire-and-forget appendOplogNote with majority WC per call to move the majority commit point and shorten registerWaiterForMajorityReadOpTime waits.

Many recovery threads hitting step 4 at once can amplify load on the primary.

Investigate deduplicating or batching these no-ops on each mongod, in the spirit of how afterClusterTime path join overlapping noop writes instead of issuing one per waiter.