chore(deps): bump hazelcast from 4.2.2 to 5.0.2

[saig0]

Reopening dependabot PR #151.

[allanbarklie]

@saig0

Hi - just a note to say that I think the hazelcast upgrade brings in changed behaviour if running on K8s.
It now automatically adds the kubernetes auto discovery plugin which may need a little configuration to run correctly.
A likely error to see is something like java.lang.IllegalStateException: Unknown protocol: HTT

For now config can be done by adding env. variables in your k8s broker deployment of the form HAZELCAST_KUBERNETES_

Providing just:
HAZELCAST_KUBERNETES_SERVICE_NAME

or just the pair:
HAZELCAST_KUBERNETES_POD_LABEL_NAME
HAZELCAST_KUBERNETES_POD_LABEL_VALUE

should be enough to provide a quick fix.

See:
https://github.com/hazelcast/hazelcast-kubernetes/blob/master/src/main/java/com/hazelcast/kubernetes/KubernetesProperties.java
https://github.com/hazelcast/hazelcast-kubernetes
https://github.com/hazelcast/hazelcast/releases

[saig0]

@allanbarklie thank you for pointing this out 👍

Please let me know if we need to change or add something in the exporter.

[allanbarklie]

@saig0
One thing you might consider is adding pass through settings for the various service discovery options listed in https://github.com/hazelcast/hazelcast-kubernetes/blob/master/src/main/java/com/hazelcast/kubernetes/KubernetesProperties.java
or maybe just some info similar to the above notes in the readme so people know what to think about.