`env` extension: `component` discriminator usability issue

When several parameters have the same name, but different `component` discriminator, then the `env` extension does not say which component the parameter belongs to when asking for user input

For example, I have the following params
```
- name: ingress.hosts
component: istio-ingressgateway
fromEnv: KUBEFLOW_HOST
- name: ingress.hosts
component: argo
fromEnv: ARGO_HOST
```

When running `hubctl stack configure` the `env` extension outputs:

```
* Setting parameter ingress.hosts
Enter value (6jy54gla452z74fsp9e99csj292548m... #random):
```
without saying what component the `ingress.hosts` belongs to.