Support correct targets & toolchains

[paulquiring]

This pull request updates the Bazel build and module configuration to improve multi-platform support, streamline toolchain management, and update dependencies. The main changes include significant refactoring of .bazelrc and MODULE.bazel to support explicit platform and toolchain configurations for both Linux and QNX targets on x86_64 and arm64 architectures, as well as updates to workflow and dependency versions.

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.4.2) and connecting to it...
INFO: Invocation ID: ad27a2e5-ca7f-407b-8b87-ebcc712ef755
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (26 packages loaded, 9 targets configured)

Analyzing: target //:license-check (63 packages loaded, 9 targets configured)

Analyzing: target //:license-check (82 packages loaded, 16 targets configured)

Analyzing: target //:license-check (133 packages loaded, 2465 targets configured)

Analyzing: target //:license-check (134 packages loaded, 4853 targets configured)

Analyzing: target //:license-check (145 packages loaded, 6911 targets configured)

Analyzing: target //:license-check (145 packages loaded, 7267 targets configured)

Analyzing: target //:license-check (145 packages loaded, 7267 targets configured)

Analyzing: target //:license-check (148 packages loaded, 9277 targets configured)

Analyzing: target //:license-check (149 packages loaded, 9401 targets configured)

INFO: Analyzed target //:license-check (150 packages loaded, 9527 targets configured).
[9 / 13] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox
[11 / 13] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
[12 / 13] Building license.check.license_check.jar (); 0s disk-cache, multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 28.338s, Critical Path: 2.66s
INFO: 13 processes: 9 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

[github-actions]

The created documentation from the pull request is available at: docu-html

[paulquiring]

For the reviewers the failed check QNX8 Build / qnx-build / Build QNX target (pull_request_target) is because of a sporadic failure. One commit before this check passed no relevant files changed.

[pawelrutkaq]

@paulquiring comments may be helpfull to fix qnx. Keep in mind that your chnages will only affect QNX CI only after merge so you shall test them locally .
IE bazel build --config x86_64-qnx //examples/... works
but bazel build --config x86_64-qnx //examples/rust_supervised_app does not

This means we need a collector in examples and mention it in CI/CD ?

[paulquiring]

@paulquiring comments may be helpfull to fix qnx. Keep in mind that your chnages will only affect QNX CI only after merge so you shall test them locally . IE bazel build --config x86_64-qnx //examples/... works but bazel build --config x86_64-qnx //examples/rust_supervised_app does not

This means we need a collector in examples and mention it in CI/CD ?

@pawelrutkaq I tested successfully locally and ensured that the examples are also build in the qnx workflow.

[pawelrutkaq]

@paulquiring please fix CI

[pawelrutkaq]

Fix red CI

[paulquiring]

Fix red CI

@pawelrutkaq I cannot re-run the failed jobs here. So I created a fork and opened the very same PR to my fork to see what happens.

[Bazel Build / Build Bazel Code (pull_request) is successful in PR on fork

Bazel Build / Build Bazel Code (pull_request) fails for this pr.

I can't say where the problem lies. It's not reproducible. Neither with CI nor with bazel build --config x86_64-linux //... on my pc is it reproducible.

EDIT:
I was able to track down the difference between the runs. The cache used is different

PR on fork
key: bazel-ob-v2-Linux-18b453302736302dba354e06c3149f0e7213ebbaa997a2dbd50c32f7f92eec85

This PR
key: bazel-ob-v2-Linux-a2882a0dd74638dcc1cb71960051c25aa3d0590c09c5a59a90602013aff17e50

I suggest to merge because the last failing check is because of a bad Cache hit.