Clarify skip-drainage deletion requirements

[Shivs11]

Summary

• clarify that --skip-drainage bypasses only the drainage-status check when deleting a Worker Deployment Version
• state explicitly that the active-poller requirement is always enforced
• document the risk to open pinned Workflow Executions when deleting a draining Version
• regenerate the tracked CLI command definitions

Why

The existing command and flag descriptions use an ambiguous double negative: “Ignore the deletion requirement of not draining.” This can be read as allowing deletion while active pollers remain, even though the server always enforces the active-poller check independently of drainage status.

This change makes the two safeguards and the scope of --skip-drainage explicit in both CLI help and the generated command-reference documentation.

User impact

Users will be less likely to mistake --skip-drainage for a force-delete option. The generated documentation page will inherit the corrected wording through the CLI documentation sync.

Validation

• go test ./cmd/gen-docs ./internal/commandsgen
• go test ./internal/temporalcli -run '^TestHelp_' -count=1
• generated and inspected dist/docs/worker.mdx
• inspected temporal worker deployment delete-version --help
• git diff --check