[WFCORE-60] Add a registry for capabilities and requirements, modifiable via the OperationContext
[WFCORE-60] Add convenience ops to base add/remove handlers
[WFCORE-60] Add ability to register needed capabilities to the subsystem test infrastructure
[WFCORE-60] Remove 'getDescription' from the capability API until we clarify its use
[WFCORE-92] cli deploy command with unpaired quotation mark causes StringIndexOutOfBoundsException
Expose org.jboss.as.network.OutboundSocketBinding#getName
Merge pull request #165 from jaysensharma/WFCORE-92

[WFCORE-92] cli deploy command with unpaired quotation mark causes Strin...
Merge pull request #167 from rhusar/org.jboss.as.network.OutboundSocketBinding#getName

Expose org.jboss.as.network.OutboundSocketBinding#getName
Merge pull request #128 from bstansberry/cap-req

[WFCORE-60] Runtime capabilities and requirements
Amend module name
[WFCORE-96] OutboundSocketBinding always overrides source socket with binding manager default, unable to bind to wildcard address
Merge pull request #171 from rhusar/WFCORE-96

WFCORE-96 OutboundSocketBinding always overrides source socket, unable to bind to wildcard address
[WFCORE-60] Support multiple registration points for the same capability or requirement

Ease of use thing for cases where the add/remove handler for a type=* resource is the logical place to register/deregister a capability or requirement. We allow multiple registration points to account for the fact that the handler may be executed multiple times for different concrete addresses. Otherwise the subsystem author needs to track how many registration points exist and only register once and only deregister when the last registration point is removed.