Deployment-related OperationHandler improvements

Primary goal is to eliminate the need for a separate "deploy" operation following an "add" for a deployment resource. Plus minor cleanups.

In all cases, the output of the DescriptionProvider associated with the handler must be updated to match changes to the handler.

org.jboss.as.server.deployment:

DeploymentAddHandler

a) After updating the model, if context.getRuntimeContext() != null and subModel.get(ENABLED).asBoolean() == true,
deploy the deployment. See DeploymentDeployHandler for how to deploy

b) Update StandaloneXml (in controller module) so it doesn't create a "deploy" operation at boot, since "add" will now deploy

c) lesser priority: handle other ways of providing the deployment content, depending on what param users provided:
– HASH (i.e. content already uploaded) – this is already implemented
– INPUT_STREAM_INDEX (i.e. stream is attached to OperationContext) – this is already implemented
– BYTES (param value is a byte[] of content) – see DeploymentUploadBytesHandler for how to store the content in the repo
– URL (server is to read content from URL) – see DeploymentUploadURLHandler for how to store the content in the repo

DeploymentFullReplaceHandler

lesser priority: handle other ways of providing the deployment content, depending on what param users provided
Same details as for DeploymentAddHandler

DeploymentRemoveHandler

remove the existing if (model.get(ENABLED).asBoolean())

{...} branch; the code should always execute the current "else {...}

" branch

org.jboss.as.domain.controller.operations.deployment:

DeploymentAddHandler

lesser priority: handle other ways of providing the deployment content, depending on what param users provided
Same details as for org.jboss.as.server.deployment.DeploymentAddHandler

DeploymentFullReplaceHandler

lesser priority: handle other ways of providing the deployment content, depending on what param users provided
Same details as for org.jboss.as.server.deployment.DeploymentAddHandler