Partition count changes not validated on calls to cluster/configuration

Cluster configurations provided via the cluster/configuration endpoint should be validated to ensure they don't change the number of partitions. Without that validation, an invalid configuration can be stored and the request will appear successful, but the partitions will never be updated. This can lead to a partial configuration change wherein the cluster membership has been changed, but partitions cannot be updated from the invalid configuration.