Allow silencing triaged warnings

[tpudlik]

Description of the feature request:

Allow the root module to control which WARNING, INFO, and DEBUG messages should be silenced.

Which category does this issue belong to?

CLI

What underlying problem are you trying to solve with this feature?

When I invoke Bazel to build my project, I often get warnings from external dependencies. Some of these warnings are actionable: I appreciate them and fix them! Others I have reviewed and decided I should take no action on. Maybe the warning is a false positive (#7157, NB still not fixed!), or I'm already tracking fixing it in an issue and don't need it displayed to every developer on my project. I wish I could silence these triaged warnings.

https://bazel.build/reference/command-line-reference#flag--ui_event_filters is the best we have today, but it's a blunt tool: AFAIK it only lets me silence all WARNING, DEBUG, or INFO messages. That's too coarse! I want to silence specific warnings that I've triaged.

Which operating system are you running Bazel on?

Linux and MacOS

What is the output of bazel info release?

8.1.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

[tpudlik]

Given that #4772 is still not implemented, the warnings I'm talking about here are not those coming from Starlark itself, but from some wrapped tool. For the C/C++ compiler, warnings can be controlled with reasonable granularity via --per_file_copt. But what about other tools (e.g. whatever generates the warning bazelbuild/rules_python#1707, which for me as a user is not actionable)?