Bazel: migrate lint/style checks to native Bazel configuration & add clean-coverage target

[NikitaJangidBMW]

Migrate code quality checks from make lint to Bazel's native linting via aspect_rules_lint,
and add a reusable cleanup target.

BUILD

• Add sh_binary target //:clean-coverage -> executes cleanup script (equiv. make clean-coverage)
• Tag helper targets (requirements_*) as manual to prevent inclusion in default build set

MODULE.bazel

• Add dependency: rules_shell@0.6.1 — needed for shell script execution

.github/workflows/ci.yml

• Rename job from "PyLint" → "Bazel Lint" for clarity
• Install Bazel via bazel-contrib/setup-bazel@0.19.0 with caching enabled
• Replace make lint with bazel build --config=lint //...

util/BUILD (new)

• Export clean_coverage.sh for use as Bazel label

util/clean_coverage.sh (new)

• Replaces make clean-coverage shell invocation

requirements_dev.txt

• Relax pylint version constraint: pylint<4.0 → pylint>=3,<4.0 for flexibility
• Lock file updated accordingly

Additional

• .bazelrc: Update lint aspects path from //tools/lint → //third_party/lint
• tools/sphinx/BUILD: Tag requirements targets as manual
• trlc/BUILD: Add filegroup py_sources
• Update documentation/dev_setup.md to remove make lint command and add Bazel clean-coverage

[hoe-jo]

For Lint and Format already aspect rules lint is setup in Bazel, see
tools/lint -> pylint + ty (maybe change to pylint + ruff)
tools/format (-> ruff and buildifier)

[phiwuu]

Please also update the section on make lint in file documentation/dev_setup.md

[NikitaJangidBMW]

For Lint and Format already aspect rules lint is setup in Bazel, see tools/lint -> pylint + ty (maybe change to pylint + ruff) tools/format (-> ruff and buildifier)

@hoe-jo Thanks, that makes sense. We should reuse the existing Bazel lint/format pipeline rather than add parallel wrappers. The only concern is that replacing ty with ruff would drop type-checking coverage, since ruff is not a type checker.