CentOS Stream 10 package dependencies / colission

[phracek]

Our Nightly builds hit the issue with nodejs package collision

See:

CentOS Streeam 10 - 20-minimal failure is caused by this one:

CentOS Stream 10 - BaseOS                        48 MB/s | 6.6 MB     00:00    
CentOS Stream 10 - AppStream                     24 MB/s | 3.1 MB     00:00    
CentOS Stream 10 - Extras packages               35 kB/s | 3.8 kB     00:00    
Package findutils-1:4.10.0-5.el10.x86_64 is already installed.
Package tar-2:1.35-7.el10.x86_64 is already installed.
Error: 
 Problem: package nodejs-full-i18n-1:22.13.1-2.el10.x86_64 from appstream requires nodejs(x86-64) = 1:22.13.1-2.el10, but none of the providers can be installed
  - cannot install both nodejs-1:22.13.1-2.el10.x86_64 from appstream and nodejs-1:22.13.1-1.el10.x86_64 from appstream
  - cannot install the best candidate for the job
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Only CentOS Stream 10 is affected also hit by PR #475
As soon as nightly Builds passed and RPM package dependencies are solved, then we can close this issue.

[khardix]

The current theory: There was a build that was untagged from c10s compose (nodejs22-22.13.1-4.el10), but not before it found it's way to the mirrors, and it's now playing havoc with the DNF solver. A new build (nodejs22-22.13.1-5.el10) is now on it's way; hopefully that will help.

[khardix]

The fixed build is now visible on mirrors, and from my local testing it seems to have fixed the issue.

[test]

[khardix]

@phracek This should be good to go, but it seems like I cannot trigger a CI run to verify.

[khardix]

Verified via recent CI run in another PR.