Bump min supported libcomps

[dralley]

[noissue]

[patchback]

Backport to 3.19: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.19/26acac6f768013d5934c485511921fff255c2e84/pr-3538

Backported as #3596

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.18: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.18/26acac6f768013d5934c485511921fff255c2e84/pr-3538

Backported as #3597

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.25: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 26acac6 on top of patchback/backports/3.25/26acac6f768013d5934c485511921fff255c2e84/pr-3538

Backporting merged PR #3538 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulp_rpm.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.25/26acac6f768013d5934c485511921fff255c2e84/pr-3538 upstream/3.25

4. Now, cherry-pick PR Bump min supported libcomps #3538 contents into that branch:

   $ git cherry-pick -x 26acac6f768013d5934c485511921fff255c2e84

   If it'll yell at you with something like fatal: Commit 26acac6f768013d5934c485511921fff255c2e84 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 26acac6f768013d5934c485511921fff255c2e84

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Bump min supported libcomps #3538 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.25/26acac6f768013d5934c485511921fff255c2e84/pr-3538

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.23: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.23/26acac6f768013d5934c485511921fff255c2e84/pr-3538

Backported as #3595

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.22: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.22/26acac6f768013d5934c485511921fff255c2e84/pr-3538

Backported as #3598

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.