Add support for Hub RPC API through apache httpd.

[rjmateus]

What does this PR change?

HUB XML-RPC API call should be done through apache and using HTTPS, as we have for saline, for example.
This allows the HUB API to use SSL and avoids opening one more port.

Depends on this PR: uyuni-project/uyuni#10395

Needs documentation adjustments.

Codespace

Check if you already have a running container clicking on

Test coverage

• No tests: add explanation

• No tests: already covered

• Unit tests were added

• DONE

Links

Issue(s): #

• 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)

Before you merge

Check How to branch and merge properly!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cbosdo]

HUB XML-RPC API call should be done through apache and using HTTPS, as we have for saline, for example. This allows the HUB API to use SSL and avoids opening one more port.

Could this affect existing deployments? I suppose that we cannot remove the hub port without breaking something

[rjmateus]

@cbosdo the PR is not finished, and it will probably need to make some "migration" step. However, keep the port exposed during a major version is not a problem, and we can remove it during the upgrade/migration process.