[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 1071330] Try to avoid timeouts on retrieving system settings

This is a bit of a shot in the dark to reduce the possibility of
timeouts when reading system settings in the server under load.

The concurrency on the bean has been changed from the default
container managed with a write lock on each method to bean managed
with a single critical section in the cache loading and writing methods.

Also, the deobfuscation of the password fields happens only on the
cache reload and only if the settings were changed.

All this to minimize the contention on the SystemManagerBean and to
speed up the retrieval of the settings as much as possible.
[BZ 1071330] Minimize the duration of the locks