Test order issue with ejb32.lite.timer.schedule.lifecycle.* tests

[starksm64]

Describe the bug
There appears to be a test ordering issue with the ejb32 com.sun.ts.tsts.ejb32.lite.timer.schedule.lifecycle.* tests. The issue I have seen is that the Client#isCalendarTimerAndGetSchedule expects the ScheduleBean.YEAR_5000 timer to be active, but the Client#timerHandle test cancels this timer. The default test method order is declared order, so the timerHandle method runs before isCalendarTimerAndGetSchedule, and isCalendarTimerAndGetSchedule fails because the ScheduleBean.YEAR_5000 timer does not exist.

Looking at how the ClientEETest would order methods, it seems to use the same default order as it just reflects on all methods if the test is not specified. I'm not sure how this would not been a problem in EE10 unless a different test order was somehow created.

To Reproduce
Running the com.sun.ts.tests.ejb32.lite.timer.schedule.lifecycle.ClientEjbliteservletTest using the https://github.com/jakartaredhat/wildfly-ee11-tck-runner will show the issue.

Expected behavior
The timerHandle test cannot run before the isCalendarTimerAndGetSchedule test.

[starksm64]

A work around is to order the tests by name using @TestMethodOrder(MethodOrderer.MethodName.class):

@ExtendWith(ArquillianExtension.class)
@Tag("platform")
@Tag("web_optional")
@Tag("ejb_persistent_timer_optional")
@Tag("tck-javatest")
@TestMethodOrder(MethodOrderer.MethodName.class)
public class ClientEjbliteservletTest extends com.sun.ts.tests.ejb32.lite.timer.schedule.lifecycle.Client {
    static final String VEHICLE_ARCHIVE = "ejb32_lite_timer_schedule_lifecycle_ejbliteservlet_vehicle";