The jstestfuzzer can do a direct write to the fcv document and set the FCV state to "upgrading from last-lts to last-continuous". This is a valid state, but we expect it to only  be accessible through the setFeatureCompatibilityVersion command by setting fromConfigServer: true, which is only used internally by sharding. 

run_validate_collections.js can fail to complete the in-progress FCV transition when running the ValidateCollections hook. We should check that if the current FCV is in the upgrading to last-continuous state, we also pass in fromConfigServer: true