[Feature Request] Multi-pod worker deployments

Is your feature request related to a problem? Please describe.

Consider a workflow DSL that lets users define their own workflows inside the product. The workflow implementation that interprets this DSL uses two kinds of activities:

1. Activities that perform heavy computation
2. Activities that only make HTTP or DB calls

The different activity workers and the workflow worker should not live in the same pod, for a few reasons:

• Each activity worker type and the workflow worker has its own security policy /
  ServiceAccount.
• If an activity container fails, it should not affect the workflow worker. When
  containers share a pod, both contribute to whether the pod is considered healthy.
• They have different scaling factors
• ......

That said, a single release that covers all workers is usually desirable, except in specific cases.

Describe the solution you'd like

Let users set the Temporal deployment name explicitly instead of always auto-generating it. With an explicit name, users could run multiple WorkerDeployment resources that share the same temporal deployment.

There might be a better way or practice how to handle such cases

Additional context

The issue names no files, tests, or entry points. Start by locating the WorkerDeployment resource and the code that auto-generates the Temporal deployment name. Done should be defined as an explicit naming option that allows multiple WorkerDeployment resources to share one Temporal deployment while preserving the single-release behavior.