DomainLifecycleUtil uses WildFlyManagedConfiguration as a source to configure how a Domain Mode process for test cases is launched.

When the process command is being prepared, it ignores the stability level defined in WildFlyManagedConfiguration when its value is "default", so the final command is built without any stability level configuration, which means the Domain will use the default stability level configured for the project, in this case, "community".

There should be a mechanism to specify "default" stability level so we can start a Domain Mode under such a desired stability level.