Automatically build and release the CLI for the linux-arm64 build target

[chtzvt]

• Did you write/update appropriate tests
• Release notes updated (if appropriate)
• Appropriate logging output
• Issue linked
• Docs updated (or issue created)
• New package licenses are added to ThirdPartyNotices.txt (if applicable)

[github-actions]

Unit Test Results

810 tests   810 ✅  22s ⏱️
  1 suites    0 💤
  1 files      0 ❌

Results for commit 74df323.

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
gei	79%	70%	519	✔
Octoshift	87%	76%	1272	✔
ado2gh	84%	78%	627	✔
bbs2gh	78%	73%	651	✔
Summary	83% (6821 / 8172)	75% (1534 / 2044)	3069	✔

[chtzvt]

RE #1230 (comment) I've essentially made a carbon copy of Tim's commit for windows-x86, but will perform some additional testing in my fork.

[chtzvt]

Or perhaps not... For some reason, none of the workflows in my fork appear in the Actions tab of my fork!

Would love to dispatch the CI workflow and actually test the built linux-arm64 release.

[dylan-smith]

Or perhaps not... For some reason, none of the workflows in my fork appear in the Actions tab of my fork!

Would love to dispatch the CI workflow and actually test the built linux-arm64 release.

When I fork repos I get this in my fork:

[chtzvt]

@dylan-smith I was able to create a separate fork of this repository, merge this PR into it, and run a modified version of the CI workflow (which removed the E2E integration tests, as their success is required for the publish step to proceed but I cannot run them).

The modified CI workflow run produced working aarch64 builds for Linux in the publish step, which I was able to verify as executable on an ARM Linux VM:

I've invited you as an outside collaborator to that repository if you'd like to access/inspect the built artifacts on your end.

[dylan-smith]

I no longer work on the gei eng team (I just lurk in the repo), so one of the engineers from that team will have to shepherd this PR in.