Refactor Camunda WildFly subsystem to use `org.jboss.msc.Service`

[yanavasileva]

Acceptance Criteria (Required on creation)

• Camunda WildFly subsystem org.jboss.msc.Service instead of org.jboss.msc.service.Service<T>

Hints

• Created on behalf of https://github.com/camunda/camunda-bpm-platform/issues/3780#issuecomment-1940789819
• The service API was not meant to be used that way we implement the Camunda subsystem. The new Service API is encapsulated.
  • org.jboss.msc.service.Service<T>
    • Use org.jboss.msc.Service instead.
    • 🔴 However, we still use #getValue (below that throws UnsupportedOperationException if org.jboss.msc.Service is used.
  • org.jboss.msc.service.ServiceController.getService()
    • it doesn't seem to be necessary in MscRuntimeContainerDelegate.
    • :question: How to rewrite in the JBossSubsystemXMLTest
  • org.jboss.msc.service.ServiceController.getValue()
    • ❓ How to rewrite it?
  • org.jboss.msc.service.ServiceController.getName()
    • in ServiceTracker: use getServiceName to do isParentOf
    • in tests: ❓ How to rewrite it?

Links

Breakdown

### Pull Requests