argo server doesn't respect --argo-server parameter

### Pre-requisites

- [X] I have double-checked my configuration
- [X] I can confirm the issues exists when I tested with `:latest`
- [ ] I'd like to contribute the fix myself (see [contributing guide](https://github.com/argoproj/argo-workflows/blob/master/docs/CONTRIBUTING.md))

### What happened/what you expected to happen?

I'm trying to run on a broadcast address 0.0.0.0 with the command `argo server -n argo --argo-server 0.0.0.0:9999` and it still launches on localhost:2746. I also tried to set `ARGO_SERVER="0.0.0.0:9999"` environment variable and no luck as well

I don't know what `:latest` is, I tried `kubectl apply -n argo -f https://github.com/argoproj/argo-workflows/releases/download/latest/install.yaml` and it says such a file does not exist

### Version

v3.4.3

### Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

```YAML
argo server -n argo --argo-server 0.0.0.0:9999
```

### Logs from the workflow controller

```text
Not a workflow-related issue
```

### Logs from in your workflow's wait container

```text
Not a workflow-related issue
```

Start at the `argo server -n argo --argo-server 0.0.0.0:9999` command entry point and trace how the `--argo-server` flag and `ARGO_SERVER` environment variable are handled. Reproduce the v3.4.3 behavior, then verify that the server binds to 0.0.0.0:9999 instead of localhost:2746.

Written by the indexing model from the issue text.