Add ARM64 Linux layout support to score_log_bridge

[Subramanian-K812]

Summary

Adds arm64-linux platform support to score/mw/log/rust/score_log_bridge/BUILD
so that the C++/Rust log bridge builds correctly on aarch64-linux targets
(e.g. eb-aarch64 / ebclfsa SDK).

Why

The adapter cc_library and score_log_bridge rust_library both use a select()
to emit the correct layout-compatibility define (x86_64_linux, arm64_qnx, etc.).
Without an arm64-linux entry, builds targeting aarch64-linux fall through to
//conditions:default: [], meaning no define is set. This causes a compilation
failure in the C++/Rust FFI interface because the struct layout is undefined.

Change

• Adds a new config_setting(name = "arm64-linux", ...) for arm64 + linux.
• Adds ":arm64-linux": ["arm64_linux"] to the defines select in cc_library
  and the crate_features select in both rust_library and rust_test.

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: e03b0a1c-96ad-49bc-a92a-0464c4f76caf
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 4 packages loaded
Loading: 4 packages loaded
    currently loading: 
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:license-check': no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/logging/logging/BUILD
INFO: Elapsed time: 5.201s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

[github-actions]

Thanks for the pull request. This thread has been quiet for 30 days, so we are marking it as stale for now. Please take a quick look and let us know whether it is still up to date, still relevant, needs review, or is ready to merge. Any new activity will remove the stale label automatically. If nothing changes in the next 10 days, we will close it to keep the backlog current.