Currently our bazel rules are incompatible with "bazel test" when running with Remote Execution. It looks like the dynamic libraries need to be explicitly listed as inputs in addition to outputs.

We don't have any CI validation around "bazel test" since it's not scoped as supported for the initial conversion, but we should add validation to make sure any bazel rule manipulation won't make it difficult for us to support remote execution for bazel test in the future.

The really nice feature this gives us over bazel run is the ability to actually execute the test on the remote execution cluster. For example, you could do "bazel test :mongod_test --platform=ubuntu22_amd64" on an arm64 workstation and it would actually run the test itself on a remote amd64 system inside of an ubuntu22 container. This greatly alleviates the need for developers to have multiple workstation hosts and makes it way easier to test out platform incompatibilities.