chore: use cross to build binaries

[lifeizhou-ap]

• used rs-cross to build binaries
• add doc for running cross build locally

I have tested all the generated binaries. Testing instructions are also documented in the doc I created in this PR

Link to generated binaries: https://github.com/block/goose/releases/tag/v_lifei.0.13 (I will clean this up later on)

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Lifei/aarch64 linux". 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

[lifeizhou-ap]

The toolchain actions-rust-lang/setup-rust-toolchain@v1 does not with cross. Not sure why.

We can use hermit in the future to set up the rust so that we have consistent environment locally and the build environment

[michaelneale]

yeah that is fine