In SERVER-106552 we fixed an invariant failure when a node that got stuck in step down process due to term change had accepted a newer reconfig before it actually updated its own term. The invariant is a part of automatic reconfig that the node was scheduling for "newlyAdded" field removal while still considering itself a primary. We need to prevent this mismatch for a general case.