ci: consolidate C++, Rust, and Python linting with rules_lint

## Context

After the clang-tidy follow-up in #538 is complete, consolidate the repository’s language-specific linting into a single CI job based on `rules_lint`.

## Scope

- Run clang-tidy, Clippy, and Ruff through `rules_lint` in one CI job.
- Produce SARIF reports for all supported linters and upload them to GitHub code scanning.
- Preserve diagnostics and SARIF upload when a linter reports findings, so all findings remain visible in CI and code scanning.
- Migrate or reconcile the existing Clippy configuration currently hosted in `eclipse-score/cicd-workflows`.
- Validate the integrated solution in baselibs first.
- Once proven, make the reusable solution available to `eclipse-score/tooling` and assess moving shared CI/configuration parts into `eclipse-score/cicd-workflows`.

## Acceptance criteria

- [x] `#538` is completed before this consolidation is merged.
- [ ] A single CI job runs clang-tidy, Clippy, and Ruff via `rules_lint`.
- [ ] SARIF from each linter is uploaded successfully and results appear in GitHub code scanning.
- [ ] Linter failures do not prevent collection and upload of the other linter reports.
- [ ] The baselibs implementation is documented or structured for adoption by `eclipse-score/tooling` and, where appropriate, `eclipse-score/cicd-workflows`.