Add a small test project to run codechecker_bazel on

[furtib]

Created a ci job (small_test), to run the codechecker Bazel rule on a tiny Bazel project (yaml-cpp)

The installation of static analyzers and CodeChecker, and such have been moved to actions/env_setup/action.yml, to avoid repeating code.

[Szelethus]

We should likely use bazel test. Also, we added two new targets, codechecker_test_yaml-cpp and code_checker_test_yaml-cpp, but are only testing the former.

[furtib]

Running it with bazel test produces errors (despite filling the log with the success message of CodeChecker), thats why I have been using bazel build.

[nettle]

Good approach! But I think this project (yaml-cpp) should not be the only one. I would suggest adding this project as one-of-many, like putting files into sub directories with patches and test launchers etc

[Szelethus]

I think its still okay to call bazel test here, just negate the return value. Preferably also add a coment as to why the return value needs negating (because there are findings by CodeChecker).

[Szelethus]

Please change "small project" to the name of the project consistently, as we will add more than one project. Otherwise LGTM!

[nettle]

Good approach! But I think this project (yaml-cpp) should not be the only one. I would suggest adding this project as one-of-many, like putting files into sub directories with patches and test launchers etc

[nettle]

Let's agree on the structure first, see #22

[furtib]

Changed to the structure we agreed on in: #22

The composite action file's name must be action.yml; it can't be changed!
The name of the folder in actions has to describe what the action.yml file does!
See Note on top of this page:
https://docs.github.com/en/actions/reference/workflows-and-actions/metadata-syntax

[furtib]

This PR is getting too big, so I'm leaving it here as a template.

Please disregard the request to change

[furtib]

Superseeded by #43 #72 #73