helm: inconvinient dagster user deployment services naming

[paralyzah]

What's the issue?

Let's say take a look naming style for web server service: https://github.com/dagster-io/dagster/blob/master/helm/dagster/templates/helpers/_service-webserver.tpl#L7, or flower service: https://github.com/dagster-io/dagster/blob/master/helm/dagster/templates/service-flower.yaml#L5.
They are in respect with naming convention, we can easily recognize the kind of service, while user code deployments using only deployment name: https://github.com/dagster-io/dagster/blob/master/helm/dagster/charts/dagster-user-deployments/templates/service-user.yaml#L5.

What did you expect to happen?

At least mimic naming from user code deployments: https://github.com/dagster-io/dagster/blob/master/helm/dagster/charts/dagster-user-deployments/templates/deployment-user.yaml#L6, at maximum introduce new template.

How to reproduce?

No response

Dagster version

1.8.0

Deployment type

Dagster Helm chart

Deployment details

No response

Additional information

Found at 1.8.0, currently in master branch.

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

[ion-elgreco]

Introducing a new name might be breaking for a use case i have