Fix/pin kustomize version

[mahdi2ba]

Description

The deploy workflows install kustomize via the upstream install_kustomize.sh script with no version specified. In that mode the script calls the GitHub releases API (unauthenticated) to resolve the "latest" version. On shared GitHub-hosted runners that anonymous call frequently gets rate-limited, so the version comes back empty and the script tries to untar a placeholder file (kustomize_v*_linux_amd64.tar.gz), failing with Cannot open: No such file or directory and killing the deploy before it starts.

This pins kustomize to a specific version across all deploy workflows, which makes the install deterministic and removes the unreliable "latest" lookup.
Changes (applied to deploy.yaml, deploy-main-channel-to-dev/test/prod.yaml,
dev-build-release.yaml):

• Pin the version: ... install_kustomize.sh | bash -s -- 5.4.3 so the installer fetches a specific release tag instead of querying for "latest".
• Authenticate the API call: pass the built-in GITHUB_TOKEN to the install step, raising the rate limit from 60 to 5,000 req/hr.
• Use the pinned binary on apply: kustomize build → ./kustomize build, so the deploy uses the pinned 5.4.3 end-to-end instead of the runner's pre-installed kustomize.

Fixes # (deploy action failure at the "Install kustomize" step)

Type of change

• Bug fix (non-breaking change which fixes an issue)

Screenshots

N/A — CI/deployment workflow change, no UI impact.

How Has This Been Tested?

Not applicable (no application code changed). Validated by:

• Confirmed the pinned 5.4.3 release tag and the linux_amd64 asset resolve (HTTP 200).
• Validated all workflow YAML files parse correctly.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[github-actions]

🎉 This PR is included in version 2.9.12 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀