Bug 1023597 - Connection properties are not persisted with non-XA datasource creation

Fixed
Also added an itest for a datasource resource in standalone mode
Picked test methods required by DatasourceTest to plugin-test-util from
master
[BZ 1054843] - Response Time Units scale - Formatting the 'total' field independently (it was passed together with min/max/avg to MeasurementConverterClient.formatToSignificantPrecision() that causes these disproportions in values).

(cherry picked from commit 0bc1dff6fcbf00467185ce3b66edbf45c822f7b8)
Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
Revert "[BZ 1035501] - Remove Add Graph to Monitor View Menu Item in Resource Tree - removing the zombie code for groups as well (commit 7355462e593 solved the issue only for resource tree). Also removing unused I18N messages."

This reverts commit bba9df55b63a4169a735ae5d9e94beb1b6472ed3.
I seem to have messed up at least part of cherry-picks for
BZ 1035501. Reverting them all and doing it again.
Revert "[BZ 1005922] - Selecting grouped fired alerts in chosen time range does not work - hiding the filters if the alerts are shown in the grouped mode and vice versa."

This reverts commit a2d9ad3c297ef33ee3c23944b775c36826631bc3.
I seem to have messed up at least part of cherry-picks for
BZ 1035501. Reverting them all and doing it again.
[BZ 1035501] - Remove Add Graph to Monitor View Menu Item in Resource Tree - Removing the option leading to the old portal war page from the context menu.

(cherry picked from commit 7355462e593ce38a8a7b88e3a0e68b4f9da2a561)
Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
[BZ 1035501] - Remove Add Graph to Monitor View Menu Item in Resource Tree - removing the zombie code for groups as well (commit 7355462e593 solved the issue only for resource tree). Also removing unused I18N messages.

(cherry picked from commit 75ec4b37b6408822220b756186cbaa6dae361d3d)
Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
[BZ 1005922] - Selecting grouped fired alerts in chosen time range does not work - hiding the filters if the alerts are shown in the grouped mode and vice versa.

(cherry picked from commit 3c5dc0d98419a209df10a832259e85cfc1608c98)
Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
[1060223] Bundle deployment in JBoss ON 3.2.0 when using Oracle as a backend fails with ARJUNA016061 exceptions
This is a completely different problem from the "no-tx-separate-pool" issue
already fixed for this BZ.  The addition of that DS attribute led
to this issue involving the XA DS and our [quartz] job scheduling
and triggering.  The issue had to do with interactions between our
scheduling of resource bundle deployments, our scheduling of the
umbrella bundle deployment status checking job (which came into
existence as a fix for Bug 1003679), and possible fast reporting
of a bundle resource deployment status from an agent.

The solution is to ensure that the bundle deployment status checking
job is scheduled after the bundle deployment scheduling has been
fully committed and the individual bundle resource deployments have
been scheduled.

Furthermore:
 -  don't use a repeating quartz trigger, as this seems to exacerbate any problem that may occur.
 -  when scheduling an operation minimize any access time on the quartz tables.

Cherry-Pick of Master 4fec3d53f49f4fc6e941983484ae80c4a9e1a271
Signed-off-by: John Mazzitelli <mazz@redhat.com>  (review)
Signed-off-by: Jay Shaughnessy <jshaughn@redhat.com> (cherry-pick)