feat(almalinux): add new mappings for repositories with almalinux distro ID

[yuravk]

The PR is to just make visible changes of new mappings for repositories with almalinux distro ID.

That's in scope of Allow upgrades of almalinux (AlmaLinux OS) #1391

[github-actions]

Thank you for contributing to the Leapp project!

Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergeable.
If you want to request a review or rebuild a package in copr, you can use following commands as a comment:

• review please @oamg/developers to notify leapp developers of the review request
• /packit copr-build to submit a public copr build using packit

Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build.
However, here are additional useful commands for packit:

• /packit test to re-run manually the default tests
• /packit retest-failed to re-run failed tests manually
• /packit test oamg/leapp#42 to run tests with leapp builds for the leapp PR#42 (default is latest upstream - main - build)

Note that first time contributors cannot run tests automatically - they need to be started by a reviewer.

It is possible to schedule specific on-demand tests as well. Currently 2 test sets are supported, beaker-minimal and kernel-rt, both can be used to be run on all upgrade paths or just a couple of specific ones.
To launch on-demand tests with packit:

• /packit test --labels kernel-rt to schedule kernel-rt tests set for all upgrade paths
• /packit test --labels beaker-minimal-8.10to9.4,kernel-rt-8.10to9.4 to schedule kernel-rt and beaker-minimal test sets for 8.10->9.4 upgrade path

See other labels for particular jobs defined in the .packit.yaml file.

Please open ticket in case you experience technical problem with the CI. (RH internal only)

Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra.

[matejmatuska]

Hello @yuravk,
I took a quick look and I see that there are no suggested changes for Alma Linux 8.
For upgrades 8.10 -> 9.X (these are the paths defined in repos/system_upgrade/common/files/upgrade_paths.json) to work without manually specifying the --enablerepo cmdline option for each required repo, the Alma Linux 8 repositories must also be mapped.

You don't really need to modify the file. We only need to know what repos are there on AL8, on which architectures each repo is present, and if there is any special mapping to AL9 repos. By special I mean something more complex than the obvious e.g. baseos -> baseos.

[yuravk]

Hello @matejmatuska

• There are the following repositories available for AlmaLinux 8 (they are the same as for CentOS 8):

appstream
baseos
extras
ha
nfv
powertools
resilientstorage
rt
sap
saphana

• most of them are available for aarch64, ppc64le, s390x, x86_64
• rt and nfv are available for x86_64 only
• powertools maps to crb in AL9
• ha maps to highavailability in AL9
• rest of repositories map "one to one"