Rebase leapp-repository to 0.19.0 upstream version

[andrewlukoshko]

Currently ELevate uses leapp-repository 0.16.0 which is outdated.
We need to rebase on top of recently released 0.19.0 version.
almalinux-ng branch should be used.
It's also necessary to drop all CloudLinux and cPanel related code because CloudLinux now uses own fork of leapp-repository https://github.com/cloudlinux/leapp-repository

[andrewlukoshko]

The following commits should be applied on top of almalinux-ng branch:
0f31a66
3b0e3da
6c7c4b9
041e84d
04c78a2
66fe44e
3ac3cb6
b92b716
449b5f1
e4ce70d
aebbf63
d7e5f72
16a1f5e
c847c4a
65ca7fa
de6e99b
67956b8
d1ae793

This is phase 1, without 3rd party vendors yet.

[yuravk]

The phase 1 done on https://github.com/yuravk/leapp-repository/tree/almalinux-ng

[toddr]

Could you please clarify what "cpanel" changes you're dropping? We weren't aware you had any.

[andrewlukoshko]

@toddr you can check some panels related PRs here:
https://github.com/AlmaLinux/leapp-repository/pulls?q=panel

[toddr]

cPanel is using the cPanel related commits. We added these to support additional repos. Per previous discussions, this was going to be how we added other repos so they would properly upgrade the rpms that they came with. Is your plan to leave these commits out?

[andrewlukoshko]

We'll continue to maintain additional repos support with configuration in vendors.d.
So basically this AlmaLinux variant of leapp-repository will switch to follow upstream with only 2 differences:

• AlmaLinux/CentOS/Oracle/Rocky/EuroLinux/etc distributions support
• Additional repos support

They are enough to reach ELevate project goals to allow migrations between major versions of different RHEL-based operating systems with extra repos like EPEL with minimal overhead and receiving latest updates from upstream (important for 8 to 9 migrations).

CloudLinux maintains own leapp-repository fork that contains all current commits + many new CloudLinux OS and panels related ones but as I said it's a fork so updating to new upstream versions will be often delayed. Not a problem for 7 to 8 migrations but 8 to 9 migrations may require more frequent updates from upstream.

So you can choose which leapp-repository repo works better for your needs.