Coherence Operator Release 3.2.3

Fixes

Fixed an issue reconciling ServiceMonitor resources
The Operator no longer attempts to cleanly shutdown Pods if the whole namespace is being deleted.
Fixed an issue where Coherence services could be suspended on start-up and Pods fail to reach ready. These services will now be automatically resumed on start-up of storage enabled members. When suspending services on shutdown, or scaling to zero, the Operator now only suspends partitioned cache services using active persistence.
Fixed an issue in the Grafana dashboards to allow for cache names containing a $ character.

Added support for specifying StartupProbes to be added to Coherence cluster Pods.
Added support for specifying readiness gates to be added to Coherence cluster Pods.
Added support for JVM argument files created when building images with JIB. This allows the Operator to run JIB images with the class path and main class configured when the image was created.
Added additional examples
Added a section in the examples for those unfortunate enough to need to run Coherence clusters in Kubernetes without the benefits of the Operator.