Health Check: disconnected solution

[ycedres]

What does this PR change?

Initial implementation of the Disconnected solution. No access to an Uyuni server or existing monitoring stack, only access to a supportconfig.

Summary of changes:

• Introduce new container packages to build images for the different health check components. Using BCI images.
• Introduce new mgr-health-check package to build CLI.
• Provide Grafana dashboard to show metrics and logs coming from a "supportconfig"
• Implement alerts based metrics.

Some screenshots:

See: https://github.com/uyuni-project/uyuni-rfc/blob/master/accepted/00101-health-check-tool.md

Documentation

• Initial documentation at https://github.com/uyuni-project/uyuni/wiki/Health-Check-Tool

• DONE

Test coverage

ℹ️ If a major new functionality is added, it is strongly recommended that tests for the new functionality are added to the Cucumber test suite

• No tests: no tests for health check

• DONE

Links

Issue(s): https://github.com/SUSE/spacewalk/issues/24380

• DONE

Changelogs

Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository

If you don't need a changelog check, please mark this checkbox:

• No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)

Re-run a test

If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:

• Re-run test "changelog_test"
• Re-run test "backend_unittests_pgsql"
• Re-run test "java_pgsql_tests"
• Re-run test "schema_migration_test_pgsql"
• Re-run test "susemanager_unittests"
• Re-run test "javascript_lint"
• Re-run test "spacecmd_unittests"

Before you merge

Check How to branch and merge properly!

[agraul]

I left a few questions inline. I think we should enable the linter as soon as we can, it will be a bit of work to bring the code up to our standards (as expected for PoC code)

[m-czernek]

Remaining tasks:

• Apply formatting and linting: [health-check] Apply linting and formatting rules #9706
• Remove uyuni from the tool name/logs
• Move the code to the python dir (note: will have to tweak the formatting rules; this code is not compatible with Python 3.6 formatting)