[TRACKING ISSUE] Fix client not complying with the cluster reconnect strategy

The tracking issue for the Java side PR.

See https://github.com/hazelcast/hazelcast/pull/21568 for details.

---

This change prevents the client from doing the periodic attempt
for connecting cluster members again when the client is
disconnect from the cluster.

Fixes https://github.com/hazelcast/hazelcast/issues/21565 (https://stackoverflow.com/questions/72538589/hazelcast-client-too-many-logs-when-reconnecting-to-cluster)

Checklist:
- [x] Labels (`Team:`, `Type:`, `Source:`, `Module:`) and Milestone set
- [x] Label `Add to Release Notes` or `Not Release Notes content` set
- [x] Request reviewers if possible