Bug 885848 - Changing WAR/EAR deployment from exploded to unexploded (or vice versa) results in resource always being DOWN/Unavailable

Removed connection settings "deploymentName" attribute
Added connection settings "deploymentKey attribute (upgraded from "deploymentName")

We don't need to know if the deployment points to a "vfsfile:/" or "vfszip:/"

Now the profile service "deploymentName" is lazily loaded when the component is started or when it goes down because of NoSuchDeployment

Tested with EAP5.1.2 on WAR and EAR.
-> Deploy new package OK
-> Delete resource OK
-> Restart application OK
[BZ 1136751] If drift definition's interval is set to a lower value than agent's interval, show resource error
Bug 1128141 - HostController gets DOWN when name attribute in host.xml is
empty

I discovered we don't have to read HC/DC's name from host.xml at all, since
this value is provided by API via 'local-host-name' attribute. So I rewrote
BaseServerComponent#findASHostName() to use API which fixes this issue.
ServerControl class was also affected by this change - it required
xmlInputFactory (before used for reading host.xml content) which became
useless and was removed.
Bug 1138784 - [eap6] NPE when loading configuration for datasources
subsystem of managed server
Bug 1032054 - Refresh button on Monitoring/Calltime page does not move 'last 8 hour' time range

Make CalltimeView implement the refresh mechanism instead of CalltimeTableView

The problem was that #refresh was defined both in Table class and AutoResfresh interface.
Bug 1144046 - Uncaught exception when selecting Administration -> Security
menu item

MenuItems directly under Administration now target to leaf views (usually
it's the first child view which does not require special permissions)
[1073691] Table deadlock issue when processing content report...
add a perf-oriented unit test
Bug 1141839 - EAP6 resource stays UP in resource tree after its configuration directory was moved

Now validate configDir (not only baseDir) when resource component is started or avail goes UP
[BZ 1126410] Update data migrator to use the latest storage node schema.
[BZ 1126410] Minor updates based on code review.
Merge pull request #125 from rhq-project/datamigrator

[BZ 1126410] Update data migrator to latest storage node schema
[1143918] Addition of new Log Event Source using JBoss ON CLI will break the UI if all properties (even unset ones) are not added
Add support for the missing properties in this use case.
Prevent ConcurrentModificationExceptions that have been showing up in the
Jenkins test runs of this class.
BZ 1141181 1129413 - don't echo passwords to the console. ask to confirm passwords
BZ 1144238 - update DataStax driver to latest 1.0.8 release
Bug 1140637 - JBoss layered product (JBoss Fuse) does not have direct option
to open new support case

Allow opening support case on JBossFuse : JBossFuseContainer resource types
Bug 1139684 - eap cli script does not get correct result code for eap domain server on windows

This is due to "WFLY-3578 jboss-cli.bat always exits with return code 0 even after a cli failure"
https://issues.jboss.org/browse/WFLY-3578

Added jboss-cli-wrapper.bat
Calling "cmd /c jboss-cli.bat" will always return 0 even if an error occurs in the CLI
Calling it through the wrapper solves the issue

Side work:
* fix standalone and domain startup: start script prefix, if set, was not added
* when an error occurs, execute command and execute script operations now copy process output into the operation result instead of the error message
* some code cleanup (avoid possible NPE)
Bug 1140578 - [eap6 patching] applying patches via bundles fails for Windows - wrong file path extracted

Use hash sign as separator instead of pipe.

Tested on Windows2008R2
An attempt to fix the intermittent failures for
AvailabilityProxyConcurrencyTest.testConcurrentAvailChecks().  I believe the
issue is that depending on random ordering, we could exceed our set timeout
for the synchronous avail check, which we don't want to do in this test. I
added a bit more console output to help diagnose a failure in the future.
[BZ 1144514] No need to remove non-deployed property files from bundle
temporary location before deployment.

This was a remnant of an abandoned approach to the functionality that is
not needed anymore.