Introduce MicroMamba

[nettle]

Why:
We should run all tests for different configurations:

• Bazel versions 6, 7 and 8
• CodeChecker versions 6.25, 6.26, 6.27
• probably different Python versions
• might be different Clang and Clang-Tidy versions
• It would be also good to install and use
• dev tools like pylint, pycodestyle, buildifier

What:

• Introduce MicroMamba to support multiple configurations
• Add example environment (dev) for Bazel and CodeChecker
• Add scripts which install, create "dev" environment and also uninstall

Addresses:
Part of environment tools evaluation for #163

[Szelethus]

What are your intentions with this patch now that Mise landed? Do you want another one of these in or is the issue solved?

[nettle]

What are your intentions with this patch now that Mise landed? Do you want another one of these in or is the issue solved?

Mise is good and convenient when working locally.
However, just recently I have failed to use in our Jenkins setup :(
MicroMamba might be an alternative...

[Szelethus]

I'm not opposed to merging a few of these, as long as we make it clear that its not expected of contributors to test with and maintain all of these tools, not until we actually make a decision on which one we want to keep, and get rid of the others.

[Szelethus]

@furtib and I are gettin little anxious about our CI budget. Are we sure about this? Can't we make it manual?

[furtib]

LGTM.
The biggest issue is the need to create a new yaml file for each environment.

[furtib]

Typo:

Suggested change

	PROCESSES="bazel java python3 CodeChecke"
	PROCESSES="bazel java python3 CodeChecker"