JGroups client sockets are not registered with the socket binding manager

Because the JGroups subsystem does not expose a socket-binding for client sockets, these sockets are not registered with the socket binding manager.
Currently, TCP, TCP_NIO2, FD_SOCK use the same bind address for server vs client sockets and use a random ephemeral port for configuring the client socket. For environment with strict networking rules, this is not ideal, and requires overriding adhoc JGroups properties. Unfortunately, overriding the client_bind_port in this way does not recognize the port-offset of the associated socket binding group.