Use YAML file to store configuration

## Enhancement Request
Currently, there are a lot of configuration fields in EventMesh, and it will increase in the future, you can look up at `eventmesh.properties`.
Such as:
```properties
eventMesh.server.idc=DEFAULT
eventMesh.server.env=PRD
eventMesh.server.cluster=COMMON
eventMesh.server.name=EVENTMESH-runtime
eventMesh.sysid=0000
eventMesh.server.http.port=10105
########################## eventMesh tcp configuration ############################
eventMesh.server.tcp.enabled=true
eventMesh.server.tcp.port=10000
eventMesh.server.tcp.readerIdleSeconds=120
eventMesh.server.tcp.writerIdleSeconds=120
eventMesh.server.tcp.allIdleSeconds=120
eventMesh.server.tcp.clientMaxNum=10000
# client isolation time if the message send failure
eventMesh.server.tcp.pushFailIsolateTimeInMills=30000
```
It is difficult to find out which is your want since most of them has the same prefix.
It is better to store them at yaml file, the advantage is that you can merge the common prefixes like below:
```yml
eventMesh:
server:
idc: DEFAULT
env: PRD
cluster: COMMON
name: EVENTMESH-runtime
http:
port: 10105
tcp:
enabled: true
port: 10000
readerIdleSeconds: 120
writerIdleSeconds: 120
allIdleSeconds: 120
clientMaxNum: 10000
pushFailIsolateTimeInMills: 30000 # client isolation time if the message send failure
sysid: 0000

```

Start by locating eventmesh.properties and reviewing how the listed EventMesh server settings are currently represented. Define the YAML structure for the common prefixes and verify that the HTTP, TCP, and system settings can be stored there without losing their values; the issue does not identify tests or other implementation files.

Written by the indexing model from the issue text.