Currently we do not append the config 'term' field to ReplSetConfig if the term is uninitialized (i.e. -1). We did this in 4.4 for compatibility issues with 4.2, in case a 4.4 binary node sent a config to a 4.2 node. This may not be necessary any longer, since versions >= 4.4 will always be able to parse a config object with a term. There might be issues with serializing uninitialized terms, however, if we expect multi-step downgrades e.g. from 4.6 -> 4.4 -> 4.2. If an uninitialized term was written down explicitly in 4.6, we might not remove it when we go from FCV 4.4 to FCV 4.2. If we do not support such a downgrade, scenario, though, then it might be safe to remove this extra logic.