Some updates to the FCV document we introduced to setFCV between v8.3 and v9.0 are done without holding the FCVChangeRegion (e.g. here). This breaks the serialization with callers that take the FixedFCVRegion (e.g. DDL coordinator creation) to serialize with FCV changes.