Add one-time move versioning override CLI support

[Shivs11]

Related issues

What changed?

• WISOTT
• For more information, you can also view the relevant PR's:

1. Server PR: Add one-time versioning override temporal#10763
2. API PR: Add one-time move to the versioning override API! api#808

Checklist

Stability

• Breaking changes are marked with 💥 in the PR title and release notes
• Changes to JSON output (-o json / -o jsonl) are treated as breaking changes

Design

• This feature does not depend on Cloud-only APIs or behavior (it works against an OSS server)
• New commands follow temporal <noun> <verb> structure (e.g. temporal workflow start)
• New flags are named after the API concept, not the implementation mechanism (good: --search-attribute, bad: --index-field)
• New flags don't duplicate an existing flag that serves the same purpose
• New flags do not have short aliases without strong justification
• Experimental features are marked with (Experimental) in commands.yaml

Help text (see style guide at the top of commands.yaml)

• All flags shown in help text and examples are implemented and functional
• Summaries use sentence case and have no trailing period
• Long descriptions end with a period and include at least one example invocation
• Examples use long flags (--namespace, not -n), one flag per line
• Placeholder values use YourXxx form (YourWorkflowId, YourNamespace)

Behavior

• Results go to stdout; errors and warnings go to stderr
• Error messages are lowercase with no trailing punctuation

Tests

• Added functional test(s) (SharedServerSuite)
• Added unit test(s) (func TestXxx) where applicable

Manual tests

Setup

Requires a server that includes temporalio/temporal#10763 and a workflow whose Task Queue is present in the target Worker Deployment Version.

temporal server start-dev --headless
temporal workflow start \
--type YourWorkflowType \
--task-queue YourTaskQueue \
--workflow-id YourWorkflowId

Use an existing Worker Deployment Version for the target:

Deployment name: YourDeploymentName
Build ID: YourBuildId

Happy path

temporal workflow update-options \
--workflow-id YourWorkflowId \
--versioning-override-behavior one_time \
--versioning-override-deployment-name YourDeploymentName \
--versioning-override-build-id YourBuildId

Expected output:

Update workflow options succeeded

Verify table output:

temporal workflow describe \
--workflow-id YourWorkflowId

Expected: OverrideBehavior is OneTime, with OverrideTargetVersionDeploymentName and OverrideTargetVersionBuildId set.

Verify JSON output:

temporal workflow describe \
--workflow-id YourWorkflowId \
--output json

Expected: versioningInfo.versioningOverride.oneTime.targetDeploymentVersion contains the deployment name and build ID.

Error case

temporal workflow update-options \
--workflow-id YourWorkflowId \
--versioning-override-behavior one_time

Expected:

Error: missing deployment name and/or build id with 'one_time' behavior

echo$?

Expected:

1

Composition

temporal workflow update-options \
--query 'WorkflowId = "YourWorkflowId"' \
--yes \
--versioning-override-behavior one_time \
--versioning-override-deployment-name YourDeploymentName \
--versioning-override-build-id YourBuildId

Expected: a batch update-options job is started. Use temporal batch describe to inspect the batch, then temporal workflow describe on an affected Workflow Execution to verify the one-time override.

[Shivs11]

apart from the API change, the other two are temporary and shall go away the second the API changes land on main!

[Shivs11]

the reason why there is no object construction happening over here is because we don't have the SDK changes that can represent this change (which is why there is that special handling for one_time that happens right after this block)

[Shivs11]

these changes are mostly readability imo

[chaptersix]

Please filk out hte "Manual tests" section. it helps the reviewer. (Me) expirement with the changes. mostly looking to UX issues.

[chaptersix]

please add some checks for -o json as well.

[Shivs11]

this is the latest server version which has my server changes, which have gone in

[chaptersix]

LGTM, primiarily looking at this from a UX and general api standards view. Up to you if you want some more eyes from matching