ServerConnector doesn't check ClusterName when Connected #2161
Description
Problem: When reconnecting to a pub-sub subscriber which is not a member of cluster (RunAsClient = true), there is no check whether the remote endpoint still works with the same cluster. When using Kubernetes with multiple namespaces, it's possible that the remote IP is reused by another node belonging to a different namespace and working with a different ProtoActor cluster.
Expectation: each node should verify remote ClusterName upon connection. If ClusterName is different, the remote endpoint should be treated as unreachable and the deadletter should be published.