Add test sharding support for rust_test

[brianduff]

Problem

rust_test targets don't support Bazel's native test sharding. When shard_count is set on a rust_test:

• Without --incompatible_check_sharding_support: all tests run N times (once per shard)
• With --incompatible_check_sharding_support: the test fails because Rust's libtest harness doesn't read TEST_SHARD_INDEX/TEST_TOTAL_SHARDS environment variables

Solution

This PR adds opt-in sharding support via a new experimental_enable_sharding attribute. When enabled, tests are executed via a wrapper script that:

1. Detects sharding via TEST_TOTAL_SHARDS environment variable
2. Touches TEST_SHARD_STATUS_FILE to advertise sharding support to Bazel
3. Enumerates tests using libtest's --list --format terse flag
4. Partitions tests by index % TEST_TOTAL_SHARDS == TEST_SHARD_INDEX
5. Runs only the tests assigned to the current shard using --exact

Usage

rust_test(
    name = "my_test",
    srcs = ["my_test.rs"],
    shard_count = 4,
    experimental_enable_sharding = True,
)

[illicitonion]

This generally looks good to me (though I don't have enough batch skills to really verify the .bat file). One thought on provider organisation :)

[illicitonion]

Let's do something like edit rustc_compile_action to return a dict of provider types to providers, and then do a key lookup, rather than sniffing an ordered list.

[brianduff]

much better - done.

[brianduff]

Remaining test breakages appear to be pre-existing issues unrelated to this change.

The windows .bat file was a pain to test, but was able to get it to work eventually. I also have a branch where I use a small rust util to launch the tests - lemme know if we should explore that either here or as a followup.

[dzbarsky]

I would love to have the util be a rust wrapper. Seems like that would avoid multiple implementations and a bash dependency

[UebelAndre]

Once upon a time we had a test wrapper and it ended up being problematic for debuggers. I'm very nervous about introducing this in this way. Is there not a test crate rules_rust could provide that would enable sharding instead?

[UebelAndre]

I think for cross-platform consistency, could this be a rust binary?

[UebelAndre]

Should this not be a build flag similar to these?

rules_rust/rust/settings/BUILD.bazel

Lines 85 to 93 in cdaf15f

	experimental_link_std_dylib()
	experimental_per_crate_rustc_flag()
	experimental_use_cc_common_link()
	experimental_use_coverage_metadata_files()
	experimental_use_global_allocator()