WFLY-4105 Add support for explicit fork channel protocols

https://issues.jboss.org/browse/WFLY-4105
Explicit fork channels can augment the parent channel by adding protocols to their fork stack.

Introduces a number of consequential and tangential changes:
* Shares runtime protocol resource registration logic for use with fork stack
* Eliminates read-only PROTOCOLS attribute of the stack resource, protocol order is implied by ModelNode.asPropertyList()
* Deprecates custom add-protocol/remove-protocol operations of stack in favor of standard add/remove protocol resource operations
* Deprecates "extended" stack/transport/protocol add operation parameters
* Normalizes transport address to match protocol address (e.g. transport=UDP instead of transport=TRANSPORT).  Redundant TYPE attribute is now deprecated.
* JGroups subsystem now uses generic describe handler
* Eliminate redundant custom read-attribute and write-attribute handlers for cache and cache-container resources

At L122 you got the full tree rooted in stackAddress, so you can just use the Resource API to get the child from stackResource. More efficient as it saves walking the tree to get back to the resource at stackAddress and saves redundant cloning of resources.