Resolve clustering capability names using the standard mechanism in wildfly-core

Currently, clustering capabilities override the default name resolution logic by overriding org.jboss.as.clustering.controller.Capability.resolve(PathAddress). Now that wildfly-core supports customizing name resolution via org.jboss.as.controller.capability.Capability.getDynamicName(PathAddress) we should use that.

This ensures that any tooling that introspects the capability registry can correctly resolve clustering capability names.