feat: Improve support of hemertic toolchains with the clang tidy linter

[Synss]

The changes are more detailed in the commit messages.

In short, this adds two optional arguments to the linter:

• gcc-install-dir arg to prevent clang-tidy to use a gcc intallation from the host.
• deps lets users actually provide the headers and files from an hermetic toolchain registered elsewhere using the rules_cc API.

both options were lifted from https://github.com/erenon/bazel_clang_tidy

Changes are visible to end-users: yes

• Searched for relevant documentation and updated as needed: yes
• Breaking change (forces users to change their own code or config): no
• Suggested release notes appear below: no

Test plan

Would require registering an hermetic gcc toolchain, which is not trivial.

But manually:

• register hermetic gcc toolchain (based on x86-64--glibc--stable-2024.05-1.tar.xz from https://bootlin.com/ for example, see also https://github.com/bazelbuild/rules_cc/tree/main/examples/rule_based_toolchain/toolchains/gcc)
• set gcc_install_dir and deps arguments to the label defined as follows (using the bootlin toolchain)

directory(
    name = "x86_64-buildroot-linux-gnu",
    srcs = ["lib/gcc/x86_64-buildroot-linux-gnu/13.3.0"],
)

• make sure that clang-tidy now uses the hermetic headers.

[aspect-workflows]

Test

⚠️ Buildkite build #477 failed.

//lint:clang_tidy.doc_extract failed to build

in deps attribute of starlark_doc_extract rule //lint:clang_tidy.doc_extract: missing bzl_library targets for
Starlark module(s) @bazel_skylib//rules/directory:providers.bzl. Since this rule was created by the macro
'bzl_library', the error might have been caused by the macro implementation

💡 To reproduce the build failures, run

bazel build //lint:clang_tidy.doc_extract

---

Test

example

8 test targets passed

Targets

//tools/format:format_test_HTML_Jinja_with_djlint [k8-fastbuild]3s
//tools/format:format_test_JavaScript_with_prettier [k8-fastbuild]11s
//tools/format:format_test_Markdown_with_prettier [k8-fastbuild]2s
//tools/format:format_test_Protocol_Buffer_with_buf [k8-fastbuild]497ms
//tools/format:format_test_Python_with_ruff [k8-fastbuild]356ms
//tools/format:format_test_SQL_with_prettier [k8-fastbuild]2s
//tools/format:format_test_Scala_with_scalafmt [k8-fastbuild]6s
//tools/format:format_test_Starlark_with_buildifier [k8-fastbuild]444ms

Total test execution time was 24s. 33 tests (80.5%) were fully cached saving 14s.

---

Test (WORKSPACE) (Test)

example

⚠️ Buildkite build #477 failed.

//src:tsconfig failed to build

error loading package 'src': at
/mnt/ephemeral/workdir/aspect-build/rules_lint/example/tools/lint/linters.bzl:5:6: at
/mnt/ephemeral/output/rules_lint/example/external/aspect_rules_lint/lint/clang_tidy.bzl:40:6: Label
'@@bazel_skylib//rules/directory:providers.bzl' is invalid because 'rules/directory' is not a package;
perhaps you meant to put the colon here: '@@bazel_skylib//rules:directory/providers.bzl'?

💡 To reproduce the build failures, run

bazel build //src:tsconfig

---

Lint [.]      Lint [example]