This is the outcome of the discussion in SERVER-47331.
Investigate changes in SERVER-47495: Ban force reconfig with "newlyAdded" fields
Ensure that force reconfigs are not given a 'newlyAdded' field
Test behavior when a user provides a 'newlyAdded' field in a force-reconfig
Test that force reconfig removes a 'newlyAdded' field if one exists but is not provided in the reconfig
Ensure the 'newlyAdded' field is always true when present, even for force-reconfigs
Rethink the transition from force reconfig to safe reconfig