STASHDEV-7788 Monitor a few extra statistics in the `HealthMonitor` logging

 * `lock.count` which is the number of in-flight lock operations
 * `executor.q.response.stats` consisting of:
    - number of responses processed since last log
    - cumulative deserialisation time (nanosec resolution) since last log
    - the single worst packet in terms of deserialisation time since last log

The intention is to find out why the `responseThread` is getting stuck.
Deserialisation should be super quick, right?
Merge branch 'STASHDEV-7788-moar-health-monitoring' into atlassian-3.x-integration
Changed hazelcast/pom.xml to move gitDescribe.skip to a property. Now we can override it using a command line variable when working with shallow clones
Merge pull request #6 from atlassian/git-commit-id-plugin-config-properties

Changed hazelcast/pom.xml to move gitDescribe.skip to a property. Now we can override it using a command line variable when working with shallow clones. The git-commit-id plugin does not handle 'git describe' correctly when no data can be retrieved.
Added a configurable delay when re-partitioning data after a node joins the cluster. Default delay is 90secs
Merge branch 'atlassian-3.x-integration' of https://github.com/atlassian/hazelcast into atlassian-3.x-integration
STASHDEV-7788 Wait for the `responseThread`s to terminate on shutdown.