Linter configuration in baselibs is upstreamed to `eclipse-score/tooling` and/or eclipse-score/cicd-workflows`.

[4og]

Context

#541 established a rules_lint-based linting workflow in baselibs and validated it with this repository's C++, Rust, and Python targets.
The reusable configuration and CI implementation should now be maintained in the shared S-CORE repositories rather than evolving as a baselibs-specific solution.

Scope

• Identify the parts of the baselibs linting implementation that are reusable across S-CORE repositories.
• Upstream reusable Bazel lint configuration, tooling, and documentation to eclipse-score/tooling.
• Upstream reusable GitHub Actions workflow building blocks and CI configuration to eclipse-score/cicd-workflows, where appropriate.
• Keep baselibs-specific target selection, exclusions, and repository policy in baselibs.
• Update baselibs to consume the upstreamed implementation at a pinned revision or release.

Acceptance criteria

• Reusable linting configuration from ci: consolidate C++, Rust, and Python linting with rules_lint #541 is available in eclipse-score/tooling and/or eclipse-score/cicd-workflows.
• Baselibs consumes the upstreamed implementation and retains only repository-specific configuration locally.
• The baselibs lint workflow continues to run clang-tidy, Clippy, and Ruff and uploads their SARIF results to GitHub code scanning.
• The upstreamed implementation is documented sufficiently for another S-CORE repository to adopt it.

Relationship

Follow-up to #541.