Optimize ServiceProviderRegistry cache operations

The ServiceProviderRegistry from the clustering API is implemented atop a Cache<ServiceName, Set<Address>>. Currently, operations to add and remove members from the set of available provider are sub-optimal, as they replicate the entire Set<Address>. As discussed at the last clustering F2F, we should optimize these operations such that only the address to be added/removed is sent to remote nodes.