fix(do-7299): replace mamezou-tech/setup-helmfile with arch-aware binary download

[jrbeilke]

What

Replaces mamezou-tech/setup-helmfile@v2.2.0 with a shell step that detects arch via uname -m and downloads the correct helmfile binary from GitHub Releases.

Files changed

• action.yml — core change: replace mamezou step with arch-aware binary download
• .github/CODEOWNERS — DriveWealth org requirement (* @DriveWealth/devops)

Why

mamezou-tech/setup-helmfile hardcodes linux_amd64 in its JS installers with no ARM64 support. The official helmfile project ships linux_arm64 binaries and cloudposse does not expose mamezou's helm-download-url input to allow overriding from outside.

Helm itself is already installed by azure/setup-helm in the dw-github-workflows wrapper (argocd-deploy/action.yml) before this action is called, so only the helmfile binary needs to be installed here.

Note

The integration tests (test-helmfile-raw.yml, etc.) require DOCKERHUB_USERNAME/DOCKERHUB_PASSWORD secrets and a live Kubernetes cluster — these are not available in this fork. The upstream tests pass on the cloudposse repo. CI failures here are pre-existing and unrelated to this change.

How to use in dw-github-workflows

After merging, replace the reference in .github/actions/argocd-deploy/action.yml:

# Before
uses: cloudposse/github-action-deploy-argocd@d92e2c99ca7adeb8a90c561246ec1e45cc19612b # v1.10.0

# After (use the merge commit SHA)
uses: DriveWealth/github-action-deploy-argocd@<merge-sha>

Also remove the stale AMD64-only runs-on pins and comments from:

• cd-preview-argocd.yaml
• common-argocd-app-release.yaml
• common-argocd-app-rollback.yaml

References

• DO-7299 (blocker 1 of 6 — ARM64 runner adoption)
• mamezou-tech/setup-helmfile (no ARM64 issue filed; JS source confirms hardcoded linux_amd64)

Checklist

• action.yml updated
• Arch detection: x86_64 → amd64, aarch64 → arm64
• helmfile-version input threaded through (strips leading v before URL construction)
• CODEOWNERS added