This test is currently failing to be run in EngFlow remote execution. It's unclear to me why it's failing, but the main differences that will cause failures are 1. slightly different host resources are available (less ram/cpu) 2. containerization (if the test depends on kernel details this can cause issues) 3. external network access since the tests are now executing outside of Evergreen's network

Once this is fixed, please remove the tag "incompatible_with_bazel_remote_test" from the test definition as well as the incompatibility select statement.

This is currently preventing us from switching all unit tests over to be run in remote execution, slowing down CI runs and costing several thousand dollars in infra spend a month.

To reproduce the issue, run the following:

bazel test --strategy=TestRunner=remote //src/mongo/transport/grpc:grpc_transport_layer_test
bazel test --strategy=TestRunner=remote //src/mongo/transport/grpc:grpc_core_test
bazel test --strategy=TestRunner=remote //src/third_party/asio:asio_socket_timeout_test

Please ask in #ask-devprod-build if you run into any issues or have any questions