Add EnableClusterConfiguration annotation to push cluster configuration meta-data from the client to the server

This feature adds the @EnableClusterConfiguration annotation to the new Spring Data GemFire Annotation-based configuration model.

The feature and Annotation name (i.e. @EnableClusterConfiguration) should not be confused with Pivotal GemFire's own Cluster Configuration Service, which records schema-like changes initiated from Gfsh or other JMX clients affecting the entire cluster and ensuring a consistent configuration when new nodes are brought online and added to the cluster.

However, this feature will have a similar effect. The schema changes introduced by using SD's Repository abstraction and specifically the mapping infrastructure with @EnableEntityDefinedRegions or Spring's Cache Abstraction with @EnableCachingDefinedRegions along with @EnableIndexing will determine the configuration cluster-side driven from a cache client application client-side (or technically, even a peer cache application).