ISPN-10602 Lazily register clustered listener for counters

[pruivo]

Only register the clustered listener when it is required. The clustered
listener has an impact on add operation performance.

https://issues.redhat.com/browse/ISPN-10602

[danberindei]

Pedro, a bit off-topic, but what's the advantage of weak counters if writes have to update the value synchronously (via the cluster listener) on all the cluster members?

[danberindei]

I forgot one more question: have you considered also removing the counter listener when the last user listener is removed?

[pruivo]

In the weak counter, the updates happen concurrently. Each node will keep track of the keys belonging to the weak counter and only perform writes in the keys where the node is the primary owner. You save 1 round trip and you avoid lock contention as well. In addition, the reads are local (reading a field in an object)

have you considered also removing the counter listener when the last user listener is removed?

I don't think users will remove listeners that often. I mean, adding a listener just to listen for a couple "time" and then remove it, it does not seem a frequent use case.
If you think otherwise, I can take look at it in this PR too.

[pruivo]

PR updated

[wburns]

Integrated into main, thanks @pruivo !