Migrate from JavaEE to JakartaEE dependencies

After Nov 16, 2021, we can't use "JavaEE" or "Enterprise Edition" branded code in our products' docs.

So... perhaps the best option would be to move to use jakartaee dependencies in poms, instead of javaee, and where possible, update dependencies on projects to use newer ones which do the same.

Assuming Tomcat 10 uses Jakarta instead of Java in its docs/implementation/specs/APIs, then that would solve the doc problem AND move us to a newer server, which likely fixes a bunch of security issues and improves performance, too.

Affected files include:

• che-lib/che-tomcat8-slf4j-logback/src/assembly/LICENSE-tomcat.txt

• che-server/assembly/assembly-che-tomcat8/src/assembly/LICENSE-tomcat.txt
• che-server/assembly/assembly-root-war/src/main/webapp/WEB-INF/web.xml
• che-server/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/web.xml
• che-server/core/commons/che-core-commons-xml/src/test/resources/test-xml-files/nuxeo-pom.xml

Setting fixversion for 2.12 (based on 7.36, GA ~ Oct 19), but if needed we potentially slip to 2.13 (based on 7.38, GA ~ Nov 30), even though that means we'll have 2 weeks of non-compliance in live 2.12 deployments.

Can we migrate from Tomcat 8 to 10?

—

Additionally, we have 3 devfiles that do work with EAP. One uses our java sidecar; the other two simply use the latest EAP containers:

• registry.redhat.io/jboss-eap-7/eap-xp2-openjdk11-openshift-rhel8:2.0-8
• registry.redhat.io/jboss-eap-7/eap73-openjdk8-openshift-rhel7:7.3.6

The referenced projects have already been updated to use jakartaee dependencies:

• https://github.com/jboss-developer/jboss-eap-quickstarts/blob/7.3.x/kitchensink-jsp/pom.xml#L106
• https://github.com/crw-samples/microprofile-quickstart/blob/xp-2.0.x/pom.xml#L93