Add sphing toolchain

[ramceb]

📌 Description

This PR adds a bazel toolchain for sphinx builds,
which allows to inject the binary which is used
for build html documentation

🚨 Impact Analysis

• This change does not violate any tool requirements and is covered by existing tool requirements
• This change does not violate any design decisions
• Otherwise I have created a ticket for new tool qualification

✅ Checklist

• Added/updated documentation for new or changed features
• Added/updated tests to cover the changes
• Followed project coding standards and guidelines

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

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

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
2026/04/08 11:22:11 Downloading https://releases.bazel.build/8.4.2/release/bazel-8.4.2-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server (8.4.2) and connecting to it...
INFO: Invocation ID: fcf119a6-3746-463f-8ac1-9563dc47ea7e
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: src
Loading: 0 packages loaded
    currently loading: src
Loading: 0 packages loaded
    currently loading: src
Loading: 0 packages loaded
    currently loading: src
Analyzing: target //src:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //src:license-check (1 packages loaded, 0 targets configured)

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

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

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

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

Analyzing: target //src:license-check (132 packages loaded, 2549 targets configured)

Analyzing: target //src:license-check (141 packages loaded, 3998 targets configured)

Analyzing: target //src:license-check (152 packages loaded, 7618 targets configured)

Analyzing: target //src:license-check (152 packages loaded, 7624 targets configured)

Analyzing: target //src:license-check (152 packages loaded, 7624 targets configured)

Analyzing: target //src:license-check (152 packages loaded, 7624 targets configured)

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

INFO: Analyzed target //src:license-check (157 packages loaded, 9762 targets configured).
[8 / 16] Creating runfiles tree bazel-out/k8-opt-exec-ST-d57f47055a04/bin/external/score_tooling+/dash/tool/formatters/dash_format_converter.runfiles [for tool]; 0s local
[12 / 16] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox ... (2 actions running)
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
INFO: Found 1 target...
Target //src:license.check.license_check up-to-date:
  bazel-bin/src/license.check.license_check
  bazel-bin/src/license.check.license_check.jar
INFO: Elapsed time: 27.569s, Critical Path: 2.41s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/src/license.check.license_check src/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

[AlexanderLanin]

Having something overwritable/injectable seems ok. However this adds yet another dependency. I would rather remove the existing dependencies. But of course I dont know how to do that 😆

[ramceb]

Having something overwritable/injectable seems ok. However this adds yet another dependency. I would rather remove the existing dependencies. But of course I dont know how to do that 😆
The problem was the circular dependency between tooling and docs-as-code. We removed the dependency from tooling to docs-as-code in eclipse-score/tooling#116.
The already existing dependency from docs-as-code to tooling we need to keep. So the dependency chain looks as follows

module which wants to generate documentation
            ↓
       docs-as-code
            ↓
          tooling

docs-as-code defines the score_toolchain incl. all of the metamodel for generating the documentation

[a-zw]

This toolchain/file is not used so far? Why do we need it?