Description of problem:

On a system that has been installed with default maven:3.5 module that gets enabled when installing either pki-servlet-engine or tomcatjss. For upgrades, we have to do a dnf module reset and then dnf module enable maven:3.8. That all works until you attempt to do a 'dnf upgrade' and the packages from maven:3.5 cannot upgrade to the packages in maven:3.8.

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:
1. dnf module enable pki-core pki-deps
2. dnf install pki-servlet-engine tomcatjss
3. dnf module reset maven
4. dnf module enable maven:3.8
5. dnf update

Actual results:

Problem: package slf4j-jdk14-1.7.25-4.module_el8.4.0+595+e59c9af2.noarch requires mvn(org.slf4j:slf4j-api) = 1.7.25, but none of the providers can be installed

• cannot install both slf4j-1.7.32-4.module+el8.8.0+18044+0a924b8f.noarch and slf4j-1.7.25-4.module_el8.6.0+1030+8d97e896.noarch
• cannot install both slf4j-1.7.32-4.module+el8.8.0+18044+0a924b8f.noarch and slf4j-1.7.25-4.module_el8.4.0+595+e59c9af2.noarch
• cannot install the best update candidate for package slf4j-jdk14-1.7.25-4.module_el8.4.0+595+e59c9af2.noarch
• cannot install the best update candidate for package slf4j-1.7.25-4.module_el8.6.0+1030+8d97e896.noarch
• package slf4j-1.7.25-4.module_el8.0.0+39+6a9b6e22.noarch is filtered out by modular filtering
• package slf4j-1.7.25-4.module_el8.6.0+1030+8d97e896.noarch is filtered out by modular filtering
  (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)

Expected results:

Package upgrade to succeed.

Additional info:

This is an annoyance for Satellite users as the maven:3.5 module is out of support and tools such as Insights flag out of support modules. The Satellite team would like to switch to relying on the maven:3.8 module that is still supported but have been unable to make the switch due to this issue.