adding score toolchains

[odra]

Changes

• adds gcc and rust toolchains module defintions
• a dedicated bazelrc file which all build configs start with "score-..." to avoid conflicts

[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.6.0) and connecting to it...
INFO: Invocation ID: 641a5883-29d0-43fb-9ec2-78b4918512d8
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'aspect_rules_lint', the root module requires module version aspect_rules_lint@1.10.2, but got aspect_rules_lint@2.3.0 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
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 (20 packages loaded, 10 targets configured)

Analyzing: target //:license-check (79 packages loaded, 10 targets configured)

Analyzing: target //:license-check (80 packages loaded, 10 targets configured)

Analyzing: target //:license-check (89 packages loaded, 10 targets configured)

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

Analyzing: target //:license-check (162 packages loaded, 6299 targets configured)

Analyzing: target //:license-check (167 packages loaded, 8259 targets configured)

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

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

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

Analyzing: target //:license-check (170 packages loaded, 8579 targets configured)

Analyzing: target //:license-check (173 packages loaded, 10281 targets configured)

Analyzing: target //:license-check (173 packages loaded, 10281 targets configured)

Analyzing: target //:license-check (174 packages loaded, 10401 targets configured)

Analyzing: target //:license-check (174 packages loaded, 10401 targets configured)

Analyzing: target //:license-check (174 packages loaded, 10401 targets configured)

INFO: Analyzed target //:license-check (175 packages loaded, 11980 targets configured).
[9 / 16] checking cached actions
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
[14 / 16] [Prepa] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar
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: 233.170s, Critical Path: 2.32s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
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>]

[AlexanderLanin]

This would replace the gcc + rust files from https://github.com/eclipse-score/reference_integration/tree/main/bazel_common? What about the others?

[github-actions]

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

[odra]

I can the other toolchains (python, qnx, etc) if this approach is acceptable

[AlexanderLanin]

open points:

• can this be pushed & pulled to/from bazel registry?
• what will happen when users of a module dont have this included? Like if some repos dont like this.