RemoteStore should not allow segmentation if groups are configured

Grouping allows for users to group arbitrary keys to the same segment so they live on the same node. This is problematic with a remote store as it also has a notion of segments based on the key. However, there is no way currently to confirm if the remote cache has the exact same grouping as the existing node or even a way to tell if it has grouping.

We need to prevent a user from configuring a remote store when the current cache has a group until we implement a way to confirm it is properly configured.