Allow for the notes to be XML - e.g. docbook snippets.
[BZ 968269] Make endpoints for pushing metric data more
 consistent
BZ 963804, 963667 improvements to the metric endpoints
* rhqctl no longer supports putting agent and storage installs in custom locations via agent-dir and storage-dir- they always go in a well-known location under the root isntall dir
* --storage-data-root-dir now allows you to set the root directory where all the storage data dirs go - this allows one to easily install even if you aren't running as root
* the installation will fail if the custom --storage-data-root-dir is not empty
* fixed the wording on some of the help text to make it more clear about things (i.e. installing storage will imply installing an agent too; if you install just a --server, lets the user know they should have a storage node somewhere else)
turn of auto-update of the agents that are installed via rhqctl; these agents are managed by rhqctl
fix help text - we don't support agent in console right now
fix logging for datastax driver and for rhqctl

The logging for rhqctl was configured to append to rhqctl.properties. I set
append to false so that the log only contains logging from the last execution
of rhqctl.
if one of the data directories is not empty, we abort the storage installer since this indicates we are probably stepping on another storage node installation
trivial tweeks to help text
make sure seed nodes are accounted for and persisted at start up

I have renamed SessionManagerBean to StorageClientManagerBean to better reflect
its purpose. The new init method which is called at server start up does a few
things including,

* making sure storage node connection info is available
Storage node info has to be available in either the rhq.cassandra.seeds property
or in the database in order to initialize the session object. An exception is
thrown if neither exists.

* persist seed nodes if necessary
Seed nodes which are specified in rhq-server.properties will be persisted if
not already in the database. This is neecessary in case we have an HA
deployment where another rhq server does not have the seeds property set in
rhq-server.properties.

* Detect if any new seed nodes have been specified
If there are new need nodes (that is, that do not match what we have in the db)
we treat this as a topology change. This could happen for instance in an HA
deployment where after installing my first server/storage node, I then install
a second server/storage node.
need to initialize storage client before comm services

Once comm services are initialized, the server can start receiving measurement
reports from agents so we need to make sure the storage client subsystem is
initalized before that.
have to user cassandra super user to set up C* schema
BZ 835647 allow to specify a configurable number of buckets for metrics instead of the old default of 60.
BZ 929203 Allow to upload plugins via REST api.
remove some obsolete code that isn't used
add shutdown operation for storage client subsystem

When the CassandraClusterHeartBeatJob puts the server into maintenance mode it
now invokes StorageClientManagerBean to shut down the storage client subsystem.
When it takes the server out of maintenance mode, it calls
StorageClientManagerBean to reinitialize the storage client subsystem. This is
done in large part to ensure that the cassandra driver session gets recycled so
that we can reconnect to C* when it comes back up.

I have also increased the interal of the heart beat job from 5 sec to 1 minute.
5 seconds was pretty agressive and I probably had it set to that fast of an
interval to faciliate testing.
remove references to log4j dep that is no longer packaged with datastax module
GUI improvements for StorageNodeDetailView

* I changed the icon for storage node (now no attribution is needed)

* Capitalization of Some Titles

* Conditional formatting for avg heap percentage use
  (x < 70% => green, x < 85% => orange, x > 85% => red)

* More intuitive names were used for the aggregate metrics used by
  storage node load

* More formal messages

* Commenting out operation Decommission, because we don't currently
  support it on the server side

* Renaming Start/Stop RPC Server operations to Enable/Disable Debug Mode
rhqctl work
- add some feedback to the install process while waiting for
  server install
- improve some messaging
- switch to using dmr client (as opposed to log scanning) for install
  completion checking
- improve -Pdev update of dev-container the server-control module to
  update the entire module
provide an option to install, but not start, the agent. This provides a window of opportunity for users to reconfigure the agent before starting or add things like keystore/truststore files to it