Fix arm64 behavior in 0.27.0+

[libfitz]

Reverts some of the changes made in #25.
Should fix #26.

BEGIN_COMMIT_OVERRIDE
fix: make Darwin/arm64 works
END_COMMIT_OVERRIDE

[canterberry]

👍 LGTM. I'm not familiar enough with the install script here to have 100% confidence it doesn't break anything, but the changeset does involve the exact problem I'm seeing when managing k9s 0.27.0+, where the release naming conventions have changed from x86_64 to amd64.

[canterberry]

For reference, here's the breaking k9s PR: derailed/k9s#1910
This PR was incorporated into the v0.27.0 release.

[libfitz]

@looztra can this be merged please?

[looztra]

I am so late on this one.

[github-actions]

Hey dear contributors ! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Error details:

No release type found in pull request title "Fix arm64 behavior in 0.27.0+". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit