Switch to Jakarta artifacts in batch subsystem and tests

TODO:

• upgrade batch-api to jakarta.batch:jakarta.batch-api:2.0.0

  <dependency>
    <groupId>jakarta.batch</groupId>
    <artifactId>jakarta.batch-api</artifactId>
    <version>2.0.0</version>
  </dependency>
  

• upgrade jberet-core to 2.0.0.Final (released on 2021-07-09 https://github.com/jberet/jsr352/commits/master).
  • main changes between 1.3.9.Final (the current jberet-core version in WildFly) and 2.0.0.Final. They add some more enhancement to jberet-core and should be safe to work with WildFly.
    • necessary changes to implement Jakarta Batch API and references to other Jakarta API
    • JBERET-501 Support Quarkus batch processing applications
    • https://github.com/jberet/jsr352/issues/134 Support additional Serialization mechanisms #134

• update jberet-core module definition and dependency

• update tests under wildfly/testsuite/ to use jakarta libs

To integrate jberet-core 2.0.0.Final (which supports Jakarta API) into WildFly ee9 preview build, add the following to override the jberet-core dependency:

ee-9/feature-pack/pom.xml

        <version.org.jberet>2.0.0.Final</version.org.jberet>

            <dependency>
                <groupId>org.jberet</groupId>
                <artifactId>jberet-core</artifactId>
                <version>${version.org.jberet}</version>
                <scope>provided</scope>
                <exclusions>
                    <exclusion>
                        <groupId>org.jboss.logging</groupId>
                        <artifactId>jboss-logging-processor</artifactId>
                    </exclusion>
                    <exclusion>
                        <groupId>org.jboss.marshalling</groupId>
                        <artifactId>jboss-marshalling</artifactId>
                    </exclusion>
                </exclusions>
            </dependency>