[helm][template]both the client and internal address should be set in the advertised.listeners

### Search before asking

- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.

### Fluss version

0.8.0 (latest release)

### Please describe the bug 🐞

In the sts-coordinator.yaml, sts-tablet.yaml
the bind.listeners have been set by this line:
```
echo "bind.listeners: INTERNAL://${POD_IP}:{{ .Values.appConfig.internalPort }}, CLIENT://0.0.0.0:{{ .Values.appConfig.externalPort }}" >> $FLUSS_HOME/conf/server.yaml &&
```

but only the client address was set in the advertised.listeners
```
echo "advertised.listeners: CLIENT://${POD_NAME}.tablet-server-hs.${POD_NAMESPACE}.svc.cluster.local:{{ .Values.appConfig.externalPort }}" >> $FLUSS_HOME/conf/server.yaml && \

```

### Solution

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Start with sts-coordinator.yaml and sts-tablet.yaml, locating the commands that write bind.listeners and advertised.listeners into server.yaml. Compare the two listener configurations and verify that the advertised.listeners entries include both the internal and client addresses for each workload; render the Helm templates to confirm the resulting configuration.

Written by the indexing model from the issue text.