chore: Update rust, rules_rust

[arrdem]

---

Changes are visible to end-users: yes/no

• Searched for relevant documentation and updated as needed: yes/no
• Breaking change (forces users to change their own code or config): yes/no
• Suggested release notes appear below: yes/no

Test plan

• Covered by existing test cases
• New test cases added
• Manual testing; please provide instructions so we can reproduce:

[aspect-workflows]

Test

⚠️ Buildkite build #310 failed.

@@rules_python~//docs:bazel_repo_tools failed to build

error loading package '@@rules_python~//docs': Unable to find package for @@[unknown repo 'dev_pip' requested
from @@rules_python~]//:requirements.bzl: The repository '@@[unknown repo 'dev_pip' requested from
@@rules_python~]' could not be resolved: No repository visible as '@dev_pip' from repository
'@@rules_python~'.

@@protobuf~//src/google/protobuf/compiler/java:java_features_bootstrap failed to build

gcc failed: error executing CppCompile command (from target @@protobuf~//src/google/protobuf/compiler/java:java_features_bootstrap) /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 56 arguments skipped)
 
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
 
gcc: error: unrecognized command-line option '--PROTOBUF_WAS_NOT_SUPPOSED_TO_BE_BUILT'

@@protobuf~//src/google/protobuf/compiler/cpp:names_internal failed to build

gcc failed: error executing CppCompile command (from target @@protobuf~//src/google/protobuf/compiler/cpp:names_internal) /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 63 arguments skipped)
 
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
 
gcc: error: unrecognized command-line option '--PROTOBUF_WAS_NOT_SUPPOSED_TO_BE_BUILT'

@@protobuf~//src/google/protobuf/compiler/java:helpers failed to build

gcc failed: error executing CppCompile command (from target @@protobuf~//src/google/protobuf/compiler/java:helpers) /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 64 arguments skipped)
 
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
 
gcc: error: unrecognized command-line option '--PROTOBUF_WAS_NOT_SUPPOSED_TO_BE_BUILT'

gcc failed: error executing CppCompile command (from target @@protobuf~//src/google/protobuf/compiler/java:helpers) /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 64 arguments skipped)
 
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
 
gcc: error: unrecognized command-line option '--PROTOBUF_WAS_NOT_SUPPOSED_TO_BE_BUILT'

227 other actions failed to build.

Failed tests (2)

//py/tests/import-pathing:py_library_import_pathing_test_suite_test_0 [k8-fastbuild]                 🔗
//py/tests/py-test:test_env_vars [k8-fastbuild]                                                      🔗

💡 To reproduce the build failures, run

bazel build @@rules_python~//docs:bazel_repo_tools @@protobuf~//src/google/protobuf/compiler/java:java_features_bootstrap @@protobuf~//src/google/protobuf/compiler/cpp:names_internal @@protobuf~//src/google/protobuf/compiler/java:helpers

💡 To reproduce the test failures, run

bazel test //py/tests/import-pathing:py_library_import_pathing_test_suite_test_0 //py/tests/py-test:test_env_vars