feat(cross-arch): add cross arch release pipeline

[0xfourzerofour]

Closes #421

Proposed Changes

• Cross arch docker and binary releases
• Remove git submodule update from build.rs due to release pipeline incompatibility (Forge command not found even when proving it is available  cross-rs/cross#1358)
• Update docker container to allow users to run app in different modes

[dancoombs]

Code LGTM. Final couple requests here:

1. How much of this is tested? What is the testing plan? Do we need to merge first and then iterate?

2. Can you write 2 docs to support this code:
   a. release.md explaining the release process
   b. Update docker.md explaining the use of the 3 docker files, an overview of how to do builds, note anything that we had to do what wasn't intuitive, etc.

[0xfourzerofour]

@dancoombs The annoying thing about github is you cannot test updated workflows unless they are first in the default branch. We will need to merge first and then I will manually run each of them. I have added an override for the git tag in the workflow dispatch for patches and inital testing deploying to dockerhub

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.25%. Comparing base (0099370) to head (47e4ff6).
Report is 28 commits behind head on main.

Additional details and impacted files

see 59 files with indirect coverage changes

Flag	Coverage Δ
unit-tests	57.25% <ø> (+0.19%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
rundler binary	0.00% <ø> (ø)
builder	51.33% <ø> (+1.24%)	⬆️
dev	0.00% <ø> (ø)
pool	64.79% <ø> (+1.08%)	⬆️
provider	0.40% <ø> (-0.51%)	⬇️
rpc	34.72% <ø> (-2.46%)	⬇️
sim	84.46% <ø> (+0.94%)	⬆️
tasks	∅ <ø> (∅)
types	86.82% <ø> (-3.44%)	⬇️
utils	16.79% <ø> (+1.82%)	⬆️

[dancoombs]

Couple of questions, approving to unblock testing, we'll likely iterate on this a few times during testing.

[dancoombs]