Failure message when an op requires a non-existent capability doesn't list registration points for dynamic caps

[standalone@embedded /] /socket-binding-group=standard-sockets/socket-binding=test:add(interface=bogus,port=12345)
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0369: Required capabilities are not available:
    org.wildfly.network.interface.bogus; There are no known registration points which can provide this capability.",
    "rolled-back" => true
}

The failure message is not fully helpful, since while there are no reg points for org.wildfly.network.interface.bogus there are points for caps whose dynamic part is org.wildfly.network.interface.

The message is created using the results of CapabilityRegistry.getPossibleProviderPoints(), which just does a map lookup of the passed in capability name.

Any fix that changes getPossibleProviderPoints() will need to be careful not to break other uses of that method.