Embedded server operations executed using different classloaders

The embedded server, when it is used by Galleon, launched via client/jboss-cli-client.jar or in the test suite, is using the application classloader. The embedded server when is launched via CLI uses the org.jboss.as.cli module classloader.

Running the embedded server using inconsistent classloaders could lead to different bugs and strange behaviors, for example, we are using different implementations of XMLStreamWriter when the embedded server is executed via CLI and via Galleon.

Specifically, this issue cannot be reproduced with the test suite, because the woodstock XMLStreamWriter is already in the classpath.

As suggested by brian.stansberry, we should use org.jboss.as.controller classloader to run the embedded server operations.