Server fails to start due to conflict on servlet feature

[jhanders34]

Describe the bug
When individually installing a set of EE7 or EE8 features, the server can fail to start due to a conflict on servlet features. An example failure is below.

[1/10/23, 4:08:27:359 GMT] 00000027 id= com.ibm.ws.kernel.feature.internal.FeatureManager E CWWKF0033E: The singleton features servlet-3.1 and servlet-3.0 cannot be loaded at the same time. The configured features servlet-3.1 and apiDiscovery-1.0 include one or more features that cause the conflict. Your configuration is not supported; update server.xml to remove incompatible features.
[1/10/23, 4:08:27:419 GMT] 00000027 id= com.ibm.ws.logging.internal.impl.IncidentImpl I FFDC1015I: An FFDC Incident has been created: "java.lang.IllegalArgumentException: Unable to load conflicting versions of features "com.ibm.websphere.appserver.servlet-3.1" and "com.ibm.websphere.appserver.servlet-3.0". The feature dependency chains that led to the conflict are: com.ibm.websphere.appserver.servlet-3.1 and com.ibm.websphere.appserver.apiDiscovery-1.0 -> com.ibm.websphere.appserver.restHandler-1.0 -> io.openliberty.restHandler.internal-1.0 -> io.openliberty.webBundleSecurity.internal-1.0 -> io.openliberty.servlet.internal-3.0 -> com.ibm.websphere.appserver.servlet-3.0

Steps to Reproduce
Use featureUtility to install EE7 or EE8 features individually instead of using installServerFeatures.

Expected behavior
The expected behavior is that the feature install will install the features in a way to allow all of them to be included in a server.xml and the server be able to start.

Diagnostic information:

• OpenLiberty Version: 22.0.0.11 - 23.0.0.1
• Affected feature(s) Too many to list, but any feature that depends on a feature that uses internal feature io.openliberty.servlet.internal-x.0

Additional context
This problem can be worked around by using featureUtility installServerFeatures command instead. It can also be worked around by installing the mpJwt-1.2 feature if using EE 8 features.

This problem was introduced in 22.0.0.11 due to the inclusion of pull request #22549. This problem is related to issue #21992. This issue is mostly being addressed for this special case introduced in 22.0.0.11, but it does not cover all the issues outlined in #21992.

[jhanders34]

#regresion

[jhanders34]

#regression