Fix CI: pin score_rules_imagefs 0.0.1, stub Android SDK, link libgcc on eb-aarch64

The communication bump pulls score_qnx_unit_tests@0.2.0 which requests
score_rules_imagefs@0.0.3, forcing the reference integration off its pinned
0.0.1, and the new mw/com Rust com-api FFI now links C++ objects into the EB
aarch64 image. That broke four previously-green checks:

- Bzlmod Lockfile Check: imagefs extension digest changed in the lock.
- QNX8 Build: imagefs 0.0.3 removed the `ext_repo_maping` attribute used by
  images/qnx_{x86_64,aarch64}/build/BUILD.
- Code Quality & Documentation: rules_android (0.6.6, via grpc-java ->
  rules_jvm_external) android_sdk_repository fails on CI because ANDROID_HOME
  points at an incomplete SDK.
- EB corbos aarch64: undefined references to the GCC outline-atomics helpers
  (__aarch64_*_acq_rel) when statically linking the C++ com/baselibs objects
  into the Rust //images/ebclfsa_aarch64:run binary.

Fixes:
- single_version_override score_rules_imagefs to 0.0.1 so the existing QNX
  image definitions keep working (fixes the lockfile and QNX checks).
- .bazelrc: common --repo_env=ANDROID_HOME= so android_sdk_repository emits an
  empty stub instead of failing; no code here uses Android.
- ferrocene_aarch64_ebclfsa: add -Clink-arg=-lgcc so the aarch64 outline-atomics
  helpers resolve in the static Rust link.
- Regenerate MODULE.bazel.lock accordingly.

Author: antonkri

.bazelrc

@@ -7,6 +7,12 @@ common --registry=https://bcr.bazel.build
 common --credential_helper=*.qnx.com=%workspace%/.github/tools/qnx_credential_helper.py
 common --credential_helper_timeout="60s"
 
+# Clear ANDROID_HOME for repository rules. rules_android (pulled transitively via
+# grpc-java -> rules_jvm_external) evaluates android_sdk_repository, which fails
+# when ANDROID_HOME points at an incomplete SDK (as on CI runners). None of our
+# code uses Android, so forcing it empty makes the rule emit an empty stub repo.
+common --repo_env=ANDROID_HOME=
+
 # Java
 build --java_language_version=17
 build --tool_java_language_version=17

MODULE.bazel.lock

@@ -50,6 +50,16 @@ http_file(
 
 bazel_dep(name = "score_rules_imagefs", version = "0.0.1")
 
+# Pin score_rules_imagefs to 0.0.1. The bumped score_communication pulls in
+# score_qnx_unit_tests@0.2.0 which requests score_rules_imagefs@0.0.3, but 0.0.3
+# drops the `ext_repo_maping` attribute used by our QNX image build files. Force
+# 0.0.1 so the reference integration image definitions keep working without a
+# larger image-definition migration.
+single_version_override(
+    module_name = "score_rules_imagefs",
+    version = "0.0.1",
+)
+
 imagefs = use_extension("@score_rules_imagefs//extensions:imagefs.bzl", "imagefs", dev_dependency = True)
 imagefs.toolchain(
     name = "score_qnx_x86_64_ifs_toolchain",

bazel_common/score_images.MODULE.bazel

@@ -31,6 +31,11 @@ ferrocene.toolchain(
         "-Clink-arg=-static",
         "-Clink-arg=-lm",
         "-Clink-arg=-lc",
+        # Provide the aarch64 GCC outline-atomics helpers (__aarch64_*_acq_rel)
+        # referenced by the C++ (communication/baselibs) objects that are now
+        # statically linked into this Rust binary via the new mw/com Rust
+        # com-api FFI layer. Without libgcc these resolve to undefined symbols.
+        "-Clink-arg=-lgcc",
     ],
     sha256 = "b1f1eb1146bf595fe1f4a65d5793b7039b37d2cb6d395d1c3100fa7d0377b6c9",
     target_compatible_with = [