ShardingTestFixture inherits from ServiceContextTest and ShardingTestFixtureCommon.

Since ShardingTestFixtureCommon maintains a task executor that could run jobs scheduled from here, the destructor for ServiceContext must always be called after all jobs scheduled on the executor are retired. This ensures no client thread exists when unit-tests attempt to destroy the service context.