Require explicit versioned deploys and propagate Succession version tags to all container registries

[Copilot]

Deployment currently derives image selection from commit SHA, while release versioning is already declared in Succession.pm. This change makes deployment explicitly version-driven and aligns image tagging/publishing across Artifact Registry and Docker Hub.

• Deploy workflow now requires a version input

  • .github/workflows/build_deploy.yml adds required workflow_dispatch.inputs.version.
  • The workflow passes that value to bin/deploy_container.

• bin/deploy_container now deploys by version tag (not SHA)

  • Requires a version via CLI arg (or VERSION env var), normalizes optional v prefix, and validates numeric-dot format.
  • Verifies v<version> exists in Artifact Registry before deploy.
  • Deploys ...:<vversion> and sets SUCC_VERSION from the supplied version.

• bin/build_container now also tags/pushes Docker Hub with release version

  • Continues pushing GCP tags.
  • Adds Docker Hub tags for both commit SHA and v<version> (DOCKERHUB_NAMESPACE default: davorg).

• Build workflow now authenticates to Docker Hub

  • .github/workflows/build_container.yml adds docker/login-action@v3 using Docker Hub credentials from secrets.

• Focused deploy-script coverage

  • Adds Succession/t/022_deploy_container.t to cover:
    • missing/invalid version rejection,
    • missing registry tag rejection,
    • successful deploy using :v<version> and SUCC_VERSION=<version>.

# .github/workflows/build_deploy.yml
on:
  workflow_dispatch:
    inputs:
      version:
        description: Version tag to deploy (for example 0.11.2)
        required: true
        type: string

# bin/deploy_container
bin/deploy_container v0.11.2
# -> deploys .../succession:v0.11.2

• Fixes Use version number to tag Docker image #166