[FEATURE] Coordinator or zk/etcd as config server to maintain all cluster and client common conf

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [X] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues.

### Describe the feature

All cluster get config from one config center.

### Motivation

It can be easy to maintain config.

### Describe the solution

During all server startup period, sync config from coordinator/zk/etcd and apply to it configmap. Start a background thread to sync config coordinator/zk/etcd periodically and store the config hash or version as fingerprint.

### Additional context

_No response_

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Begin with the server startup configuration flow described in the issue and determine how coordinator, ZooKeeper, or etcd would provide the shared configuration. Define how periodic synchronization, application to the config map, and a configuration hash or version should work. Done means all servers and clients can obtain common configuration from one center and refresh it reliably.

Written by the indexing model from the issue text.