SERVER-47890 fixed some issues and allowed us to set the new server parameter coordinateCommitReturnImmediatelyAfterPersistingDecision to true for change stream suites following its introduction in SERVER-37364. However, since this server parameter only exists in master, the generated change stream multiversion suites are failing when 4.4 nodes attempt to set this server parameter.

Ideally we don't want to disable the multiversion suites or lose coverage of this new server parameter. One solution might be to remove the server parameter from the standard change streams suites and add a new passthrough which sets it. Then the multiversion suites would not use the parameter, and we would have coverage of the change stream suites both with the parameter set to true and omitted (thereby defaulting to false).