Bug 1109080 - Re-schedule operation fails if example schedule was run before an operation definition change in plugin descriptor

Check if example parameters are null or pass validation.
Show warning message otherwise
BZ 1068816 - fix remote client to support remote plugin API
[BZ 1078437] Correct the navigation in content subsystem JSF pages

The /portal prefix is only valid in the <redirect/> navigation cases
because in those cases it is represented literally as the URL to go to.

In all other cases it is a logical name that wasn't affected by the move of
the JSF UI to the /portal context root.
[BZ 738826] Start/Stop/Restart operation should support RPM System V init script with different service names.
[BZ 1068816] ServerPlugins -> ServerPluginManager to have consistent names
[1110434] Remote AlertDefinitionManager API does not handle template or group level definitions correctly
- Repair the AlertDefinitionManagerRemote API such that enable/disable/remove
  methods operate on any combination of template,group or resource level
  alert definitions.
- Properly jdoc the remote API methods, and improve some locals jdoc as well
- Improve the transactioning to avoid a single umbrella transaction when
  invoking the API on multiple group and/or template alert definitions.
- Convert GUI to use the enhanced remote API methods to benefit from
  the transactioning improvments and to shrink the generated Async API.
- Improve i-test to use remote api and ensure child, resource-level
  alert defs are being handled properly.

Also:
- fix a problem with authz on alert template viewing. It should not
  require MANAGE_SETTINGS to view alert defs via  getAlertDefinitionById().
- fix a long-standing bug where child alert-defs of templates or groups were
  not properly detached at remove-time of the parent, which could cause
  GUI failures when visiting the resource-level alert definitions.
- remove some unused named queries from AlertDefinition
Remove charts-4.11.css from CoreGUI.html as charts-4.12.0.css is already included.
[1110905] Agent auto update fails on windows
Add a longer pause on windows between stopping the legacy agent and
starting the update.  On Windows the wrapper must terminate and windows
must release file locks, this seems to account for some significant
extra time needed.
Add intentional API changes
Add intentional API changes (second try, fix cut+paste problem)
[BZ 1100432] Increase the availability operation timeout to 15 minutes. Due to changes in availability (now always async) the implementation is simpler for current code base then the past where async was a special case.

The 15 minutes give ample time for the server to reply to plugin request. Anything bigger than this timeout would help the avail checking and the server should be marked down.
[BZ 1100432] Reduce the timeout period to 10 minutes to be more in line with new async avail thread limits.
[BZ 1100432] Reduce the http timeout 1 minute to match server async timeout.

Add heuristics to report the server DOWN after a 5 minutes of http timeouts. And mark all the resources that have the availability request time out as UNKNOWN to defer to previous reading.
[BZ 1100432] Make log instances available locally.
[BZ 1105269] Switch to ReadResource to avoid false positives from missing deployments.
[BZ 961294] Expose config file option to the config mode for the wrapper script.
[BZ 961294] Move clean config option to the wrapper sh. The ec2 wrapper was using this option in an unreliable mode and could have resulted in errors in the wrapper or agent.
[BZ 961294] Add missing options to the help line.
Merge pull request #49 from rhq-project/BZ1100432

[BZ 1100432] Increase the availability operation timeout ...
Merge pull request #52 from rhq-project/BZ961294

Silent configuration via agent wrapper script