If two hooks with the FileBasedThreadLifecycle type are used in an FSM suite simultaneously, then because they both use the same set of files to synchronize with the FSM framework (the set of files to use is determined by the dbpath) they will end up colliding and messing up the coordination with the FSM framework.

For example, after SERVER-95248 ContinuousAddRemoveShard will use the FileBasedThreadLifecycle. This mean a suite like concurrency_sharded_stepdown_terminate_kill_with_balancer_and_config_transitions which uses ContinuousStepdown and ContinuousAddRemoveShard will fail.