Making the StorageNodeManagerBeanTest#testInit test passing; building the rhq-storage plugin by default
Just adding the cassandra plugins to plugin validator (validating the plugin descriptor, resource type, etc.)
just some name changes to distinguish templates and maybe make things more clear.
Fix issues in DiscoveryBossBeanTest that could cause test interaction
problems.
- Incorporate test class name into plugin/entity naming
- use unusual ids
- delete entities based on unique naming, not in ways that could wipe another
  test class's data
Add the actual Process to the ProcessExecutionResults and
ProcessExecutorResults. This allows the caller to inspect or detroy
the process if necessary.

Can be useful when spawning a process that does not run to completion, like
a Cassandra instance, and then stopping it later.
- fix spelling of artifactId: rhq-cassandra-ccm-arquillian
- add ProcessExecution.addArguments() which is needed for Windows, as
  setArguments() will blow away the internally added [cmd.exe, /c] args.
Make sure we always use forward slashes when generating the dev-container
rhq-storage.properties file.  Backslashes are treated as escapes by
Properties.load().
eclipse: update stax cassandra driver version
Add support for server itests on Windows.  Arquillian+Surefire+Cassandra+Windows
did not like the way we used the suite deployment extension as a hook for
starting and stopping a test cassandra cluster.  The spawned cassandra
process seems to confuse things such that the arquillian process and its
deployment (eap) process would hang, and the surefire report would
not be generated.  Likely due to the fact that Windows does not deal with
"background" processes the same way as linux.  This was after already trying
to trim the test cluster from 2 nodes to 1 node, for similar process-related
issues.

So, on Windows we have decided that to run the i-tests you must use an external
storage node (for example, a dev container instance, or a test product install).
To do this you specify:

    -Ditest.use-external-storage-node=true

By default the external storage node seed is 127.0.0.1|7199|9042.  To specify the
a different storage node upi can specify:

    -Drhq.cassandra.seeds="host|jmxport|cqlport"

This should also work for linux, if desired.

Also:
- Cassandra on Windows will not generate the pid files that were in
place to handle the killing of the test cassandra.  So, I added an enhancement
to the ProcessExecution utilities to return the actual Process, which is now
used to destroy the spawned cassandra processes.  Note that did not end up
being used in the final windows solution.  But I left it as is, because I think
even for linux it's more simple and safer than the pid file approach.

- Added autoimport of "RHQ Storage Node"
- Added test for autoimport of "RHQ Storage Node"
- Also, for windows, I had changed around the way we hooked the storage node
  handling into CCMSuiteDeploymentExtension. Again, not used in the final
  solution but I think it's a bit safer/clearer so I'll leave as is.
turn off default use of FilePreferences for agent wrapper
Fix discovery issues
add rhq storage plugin to ear
Fix artifact name for storage plugin
- Fix issue with storage node setup
- Go back to using pid files to kill cassandra processes on linux
trivial - fix type in log message
remove placing the dep plugins in the jar lib.  The useClasses feature will
get the classes from the previously loaded plugins as needed.
CassandraNodes (and StorageNodes) can't defer to JmxDiscoveryComponent.upgrade()
because the resource keys are not JvmResourceKeys.  Override upgrade() and
just return null, there is no resource upgrade, these are new resources.
changing transaction demarcation for basline and OOB calculations

The queries and methods in MeasurementBaselineManagerBean and in
MeasurementOOBManagerBean were too coarse-grained. In a test environment, I
was seeing regular timeouts while querying for schedules that do not yet have
baselines. And the method that computes OOBs was experiencing frequent
transaction timeouts. The transaction demarcation has been changed so that we
are doing a small, fixed size amount of working for each transaction when
calculating baselines and OOBs. Calls to Cassandra have been moved to
non-transactional methods.

Lastly, fixing a bug in MetricsBaselineCalculator to make sure we always return
a baseline for each schedule that it receives.
Update storage installer for Linux to start cassandra with a relative classpath. Before this change the Cassandra deamon was started with all the jar classpaths as absolute.
Add debug logging to server metrics classes. Also, a little cleanup for the metrics server class.