It's a bit silly that we have capability resolution functionality from the object returned via OperationContext.getCapabilityServiceTarget() but we do not have a similar facility available from DeploymentPhaseContext.

Ideally, we should extract a sub-interface of CapabilityServiceBuilder containing the capability-related requires(...) methods, which should resolve ServiceNames via the CapabilityServiceSupport object.
This should simplify the process for creating services within a DeploymentUnitProcessor.