Rebrand the product to Multi-Linux Manager

[deneb-alpha]

What does this PR change?

Rebrand the product to Multi-Linux Manager

GUI diff

No difference.

• DONE

Documentation

• No documentation needed: only internal and user invisible changes

• 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: internal script

• but tested on IBS at https://build.suse.de/project/show/home:deneb_alpha:branches:Devel:Galaxy:Manager:Head_rebrandTags

• see also registry namespaces in https://registry.suse.de/cgi-bin/cooverview?srch_term=project%3D%5Ehome%3Adeneb_alpha%3Abranches%3ADevel%3AGalaxy%3AManager%3AHead_rebrandTags*

• DONE

Links

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

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

[aaannz]

LGTM

Just checking, is the labelprefix without dashes? (com.suse.multilinuxmanager)

[deneb-alpha]

LGTM

Just checking, is the labelprefix without dashes? (com.suse.multilinuxmanager)

funny story... I think that prefix is not used currently. at least, I didn't find traces of it in the existing dockerfiles. but, just in case, I can branch all the containers, not just init and server.

./init-image/Dockerfile:49:# labelprefix=com.suse.multilinuxmanager.init
./server-image/Dockerfile:96:# labelprefix=com.suse.multilinuxmanager.server
./proxy-httpd-image/Dockerfile:47:# labelprefix=com.suse.multilinuxmanager.proxy-httpd
./proxy-salt-broker-image/Dockerfile:38:# labelprefix=com.suse.multilinuxmanager.proxy-salt-broker
./proxy-squid-image/Dockerfile:55:# labelprefix=com.suse.multilinuxmanager.proxy-squid
./proxy-ssh-image/Dockerfile:43:# labelprefix=com.suse.multilinuxmanager.proxy-ssh
./proxy-tftpd-image/Dockerfile:42:# labelprefix=com.suse.multilinuxmanager.proxy-tftpd
./server-attestation-image/Dockerfile:25:# labelprefix=com.suse.multilinuxmanager.server-attestation
./server-hub-xmlrpc-api-image/Dockerfile:17:# labelprefix=com.suse.multilinuxmanager.server-hub-xmlrpc-api
./server-migration-14-16-image/Dockerfile:23:# labelprefix=com.suse.multilinuxmanager.server-migration-14-16
./server-postgresql-image/Dockerfile:18:# labelprefix=com.suse.multilinuxmanager.server-postgresql
./server-saline-image/Dockerfile:35:# labelprefix=com.suse.multilinuxmanager.server-saline

not sure what should go there TBH. 🤔

I checked https://specs.opencontainers.org/image-spec/annotations/ but it only mentions to use reverse domain notation but to my knowledge that could also include dashes I think.

EDIT2: it seems that the usage or not of dashes is up to us. let's keep the label simpler omitting dashes.

I'll merge the PR as it is now