If the primary config server stepped down in the middle of ConfigSvrSetFeatureCompatibilityVersionCommand, FeatureCompatibilityVersion::set will still be called. This triggers an fassert in logOp.

It looks like the fassert can be avoided if the command does a canAcceptWritesFor check when doing writes.