Support separate client and peer cluster endpoints

Feature request type

Enhancement

Problem

A node behind per-node port translation may need to advertise a client hostname and port that differ from its directly reachable peer endpoint. Using the client endpoint for gossip or replication can break cluster communication.

Proposed solution

Add optional client address, hostname, and port advertisements for cluster discovery and redirects while retaining separate peer endpoints for cluster traffic. Preserve existing defaults and version 1 cluster configuration compatibility. Document the requirement to upgrade all nodes before relying on translated client endpoints.