By default `catchUpTimeoutMillis` is set to -1 (infinity). If user disabled catchup takeover, without setting `catchUpTimeoutMillis`, and for whatever reason the primary is stuck in catchup/drain mode, then the system can freeze. Although users can manually issue `replSetAbortPrimaryCatchUp` command to abort catchup, this is still not good user experience because it involves user intervention and long unavailability window. We should either warn users when they disable catchup takeover without setting `catchUpTimeoutMillis` or alternatively fail the configuration when that happens.