Restore the jpa-platform test usage of the ServiceEETest class

[starksm64]

No description provided.

[scottmarlow]

This makes sense also, will give this a shot.

[scottmarlow]

For reference, in EE 10, I think there are around 10,989 Persistence tests that WildFly runs for Platform TCK testing.

Currently with the EE 11 Platform TCK refactoring OpenRewrite recipe, I see that we parsed around 2117 tests as per "grep testName:" tck.log | wc -l.

Need to understand this better.

[scottmarlow]

Looks like we do need to process the JavaDoc entries also when parsing Java comments.

[scottmarlow]

With a change to also parse Javadoc comments the count of processed persistence tests is 2177 which may be correct as we are generating around 1294 new test files each of which is dedicated for a specific vehicle.

From a further check of the generated JPA source files, we have 10794 new tests that are tagged as @test which is close to the 10989 test count mentioned above. So, we can proceed forward now.

[scottmarlow]

eclipse-ee4j/jakartaee-tck-tools#84 addressed ^ test count concern.

[scottmarlow]

As a cross check, in the 10.0.x branch, I see 2180 @testname tests under the src/com/sun/ts/tests/jpa folder.

[scottmarlow]

The jpa/** tests were changed to (indirectly) extend the ServiceEETest class. The jpa-tck/** tests were created which do not extend the ServiceEETest classes.