CheckMetadataConsistency hook relies on the discovery topology which uses isMaster behind the scenes - to asses if the fixture cluster is sharded.

In the `asio_transport_layer_integration_test.cpp` unit test, a failpoint is enabled that causes `isMaster` command to fail during a specific window of time. If the checkMetadataConsistency is run between that windows of time, the test will fail.

Similar to SERVER-81340, the goal of this ticket is to skip running the CheckMetadataConsistency hook in the specific test `asio_transport_layer_integration_test.cpp` within the integration_tests_sharded suite.

SERVER-81340 attempted to resolve the issue by banning the CheckMetadataConsistency hook from running in some tests. However, this approach overlooked the fact that the path changes for Windows variants, causing the hook to still run. This ticket is intended to address this issue across all variants.