Add CreateWorkerDeploymentVersion API with compute config and CREATED status

[ShahabT]

Summary

• Add CreateWorkerDeploymentVersion frontend API that explicitly creates a version in an existing deployment with optional compute config and scaling group validation
• Add WORKER_DEPLOYMENT_VERSION_STATUS_CREATED status for explicitly created versions that transitions to INACTIVE once a poller registers a task queue
• Validate scaling groups in compute config have no overlapping task queue types (extracted as reusable ValidateWorkerDeploymentVersionComputeConfig in util.go)
• Pass compute config through the full flow: frontend → client → deployment workflow → activity → version workflow initial state

Test plan

• Unit tests for CreateWorkerDeploymentVersion success, idempotency, and rejection cases in workflow_test.go
• Functional tests for success, idempotency, already-exists, deployment-not-found, invalid args, auto-created conflict, multiple versions, and task queue registration in worker_deployment_version_test.go
• Functional tests for invalid/valid scaling group configurations
• Functional test verifying CREATED → INACTIVE status transition on poll
• Compute config round-trip verified via DescribeWorkerDeploymentVersion

[02strich]

I am not seeing the place where the actual worker controller instance would be created/deleted - can you add that?

Also for the risk of just having it missed it: is there anything in the read path that needs to change? Today the API doesn't really return much status about the compute config so maybe not...

[02strich]

do you plan to funnel this through the worker deployment version WF as well, or do the update directly?

[ShahabT]

funnel through. describe version need to have up-to-date compute info.

[02strich]

seems inconsistent to have these here and not in makeVersionWorkflowArgs?

[02strich]

do you also need to update common/api/metadata.go?