Detect analyzers not just in /bin for monolithic rule

[furtib]

Why:
When running our tests, e.g. with micromamba, analyzers are not getting found due to PATH not being passed to the monolithic rule.
This went unnoticed so far, since /bin was being added to the path in the Python script.

What:

• Mimicking the way the codechecker binary is found, I find clang and clang-tidy too.
• Ran ormatter on codechecker_script.py

Addresses:
Fixes: #234

[Szelethus]

Whoa. I just verified that all this time while using micromamba, we never actually used pretty much anything from the dev.yaml file -- despite the file specifying clang 21, the metadata files indicate that it found the system clang (which is on 18.1.3) instead:

$ cat $(find -L bazel-bin -type f -name "metadata.json") | jq | grep "analyzer_statistics" -A8
          "analyzer_statistics": {
            "failed": 0,
            "failed_sources": [],
            "successful": 1,
            "successful_sources": [
              "/path/to/rules_codechecker/test/unit/config/zero_div.cc"
            ],
            "version": "18.1.3"
          }

So this is far more severe than a simple error.

[Szelethus]

LGTM
@nettle I think this is a necessary evil we should consider living with. WDYT?

[nettle]

This is definitely not a fix.
And I'm not convinced that we should merge this workaround.
I suggest to look at line: "{codechecker_bin}": CODECHECKER_BIN_PATH,
I guess there is how the problem should be fixed or at least worked around.

[Szelethus]

Cheers @nettle for the input, this ended up looking much more ideal of a workaround.

I tested it out, analyzer version is correctly showing what micromamba set up!

bazel clean --expunge
source .ci/micromamba/init.sh
bazel test ...
cat $(find -L bazel-bin -type f -name "metadata.json") | jq | grep "\"version\""

Have made the requested changes.