[Bug] Kyuubi Server register HA&ZK serverUri and insert db in metadata table error when serverHost bind 0.0.0.0

### 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/kyuubi/issues?q=is%3Aissue) and found no similar issues.

### Describe the bug

When serverHost bind 0.0.0.0 to listen all NIC(ip double stack ipv4 / ipv6) request。
1. Kyuubi Server register HA&ZK serverUri is 0.0.0.0:10009。
2. insert db in metadata kyuubi_instance && request_conf (kyuubi.server.ipAddress, kyuubi.session.connection.url ) column value error 。
3. get connectionUrl is 0.0.0.0:port in XXXFrontendService

### Affects Version(s)

1.9.0 and above

### Kyuubi Server Log Output

_No response_

### Kyuubi Engine Log Output

_No response_

### Kyuubi Server Configurations

```yaml
kyuubi.frontend.bind.host=0.0.0.0
or
kyuubi.frontend.thrift.binary.bind.host=0.0.0.0
kyuubi.frontend.thrift.http.bind.host=0.0.0.0
kyuubi.frontend.mysql.bind.host=0.0.0.0
kyuubi.frontend.trino.bind.host=0.0.0.0
kyuubi.frontend.rest.bind.host=0.0.0.0

```

### Kyuubi Engine Configurations

_No response_

### Additional context

_No response_

### Are you willing to submit PR?

- [x] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
- [ ] No. I cannot submit a PR at this time.

Start by tracing the configured frontend bind hosts and the registration path for HA/ZK serverUri, then inspect how kyuubi_instance, request_conf, and XXXFrontendService derive their address values. Reproduce with a bind host of 0.0.0.0 across the listed frontend configurations; done means the registered URI, metadata values, and returned connectionUrl expose a usable server address rather than 0.0.0.0.

Written by the indexing model from the issue text.