SERVER-139102Open
Remove multiversion handling for afterOpTime once 9.0 is not lastlts
Placeholder ticket for making a TODO h3. Background As part of SERVER-29729, the {{afterOpTime}} readConcern field was removed from the IDL and all internal support for it was removed. The {{afterOpTime}} field was the attack surface behind three CVEs. h3. Problem Several JS tests were updated to accept *both* {{ErrorCodes.IDLUnknownField}} (the new behavior, where {{afterOpTime}} is an unknown field) and {{ErrorCodes.FailedToParse}} (the last_lts / v9.0 behavior, where {{afterOpTime