build: integrate central S-CORE toolchain configuration

[srinivasugithub]

📥 S-CORE Toolchain Configuration Integration

This PR integrates the central S-CORE toolchain configuration from the reference eclipse-score/module_template repository into the score_lifecycle repository.

Our integration ensures that all central toolchains and configurations are adopted 100% unchanged and are elegantly separated from repository-specific additions and overrides.

🌟 Key Changes

1. MODULE.bazel Alignment:

   • Replaced previous custom toolchains with the central S-CORE Toolchains (DO NOT MODIFY) section.
   • Registered the local/specific score_gcc_aarch64_toolchain separately under a clearly defined "Repository-specific toolchain additions" section.
   • Resolved a package scope issue by explicitly importing score_qcc_aarch64_toolchain_pkg inside our repository-specific section of MODULE.bazel.

2. Imported Central .bazelrc Configuration:

   • Created score.bazelrc/score_toolchain.bazelrc exactly matching the reference file.
   • Loaded the configuration gracefully inside .bazelrc via try-import.

3. Optimized .bazelrc profiles:

   • Refactored and simplified x86_64-linux to cleanly inherit from --config=score-linux-x86_64.
   • Refactored and simplified x86_64-qnx to cleanly inherit from --config=score-qnx-x86_64.
   • Completely deleted redundant configuration and the previous toolchain_common block.
   • Retained arm64-linux and arm64-qnx as separate repository-specific additions (inheriting from _score_common).

---

📊 Configuration Comparison & Gaps Identified

Feature	Central Config	Repository Config	Status / Resolution
x86_64 Linux GCC	✓	✓	Aligned & inherited
aarch64 Linux GCC	✗	✓	Retained as repository-specific in MODULE.bazel
QNX x86_64	✓	✓	Aligned & inherited
QNX aarch64	✓	✓	Aligned & inherited
Elektobit aarch64	✓	✗	New central toolchain supported
AutoSD10 x86_64/arm64	✓	✗	New central toolchains supported
QNX IFS Toolchain	✗	✓	Retained as repository-specific in MODULE.bazel
LLVM Toolchain	✗	✓	Retained as repository-specific in MODULE.bazel
Rust Ferrocene	✓	✓	Aligned & inherited

---

🔮 Identified Candidates for Future Centralization

We identified these repository-specific components that could be candidates for future S-CORE integration into module_template:

1. aarch64 Linux GCC Toolchain: Other projects targeting ARM64 Linux systems will benefit from standardizing this.
2. QNX IFS (imagefs) Toolchain: Useful to standardise image generation across QNX-based projects.
3. Sanitizer Configurations: Our custom ASAN, TSAN, UBSAN, and LSAN setup is robust and general enough to be centralized.

---

🧪 Verification Done

• C++ builds: Successfully compiled //examples/cpp_lifecycle_app using --config=x86_64-linux on host.
• C++ unit tests: Successfully executed //score/launch_manager/src/daemon/src/common:identifier_hash_UT with --config=x86_64-linux.
• Bazel Parsing: Verified that all config profiles load successfully with no syntax or constraint resolution issues.

[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.7.0) and connecting to it...
INFO: Invocation ID: 207bc302-2c30-4b76-8eab-fd329804a828
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
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: 
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 (46 packages loaded, 10 targets configured)

Analyzing: target //:license-check (139 packages loaded, 225 targets configured)

Analyzing: target //:license-check (155 packages loaded, 3236 targets configured)

Analyzing: target //:license-check (156 packages loaded, 7695 targets configured)

Analyzing: target //:license-check (161 packages loaded, 9365 targets configured)

Analyzing: target //:license-check (168 packages loaded, 9417 targets configured)

Analyzing: target //:license-check (169 packages loaded, 9541 targets configured)

INFO: Analyzed target //:license-check (173 packages loaded, 11555 targets configured).
[6 / 14] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache
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: 24.020s, Critical Path: 0.27s
INFO: 16 processes: 4 disk cache hit, 12 internal.
INFO: Build completed successfully, 16 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>]

[danth]

Fixes #448

[RamakrishnanPK]

Fixes #448

[AlexanderLanin]

@srinivasugithub can you merge this with upstream main please, there are some conflicts and some suspicious changes like downgrade of docs as code.