feat: start the service through configuration

[Kree0]

Required checklist

• Sample config files updated (config,meta/config and default config)
• If there are user-facing changes, the documentation needs to be updated prior to approving the PR( Link )
• If there are any breaking changes to public APIs, please add the api change label.
• Signed CLA (if not already signed)

Which issue does this PR close?

Related #.

Rationale for this change

Are there any user-facing changes?

[zipper-meng]

Write something to the PR conversations to describe what you've changed to the configurations, and the behavior of cnosdb or cnosdb-meta after we edit the config file as your forecasted in this PR, for example:

# Rationale for this change

## Make some configuration items optional

```toml
[cluster]
# http_listen_port = 8902
# grpc_listen_port = 8903
# flight_rpc_listen_port = 8904
# tcp_listen_port = 8905
# vector_listen_port = 8906

If comment the config grpc_listen_port or http_listen_port, then it panics when start, so cool.

The application panicked (crashed).
Message:  called `Option::unwrap()` on a `None` value
Location: /Users/magz/Rust/cnosdb/cnosdb/meta/src/model/meta_admin.rs:417

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
fatal runtime error: failed to initiate panic, error 5
[1]    88324 abort      cargo run --bin cnosdb -- run -M singleton --config ./config/config_8902.toml

[zipper-meng]

That's good

[zipper-meng]

It's ok.