Setup CI to automatically publish `forc` binary for supported architectures under each release

[mitchmindtree]

It would be super useful to have the published binaries available under the "Assets" for each release here https://github.com/fuellabs/sway/releases.

Ideally this would include builds for the common Linux, macOS and Windows architectures.

I'd imagine this would look like a new github action CI job for each architecture once the "publish" conditions have been met.

It would be nice if fuel-core was similarly available, but this might be better off under the fuel-core repo.

Useful Links

• https://trstringer.com/github-actions-create-release-upload-artifacts/
• https://github.com/johnthagen/min-sized-rust

[mitchmindtree]

This should also include builds for the new plugins, i.e.

• forc-lsp (Move forc's LSP support into a dedicated forc-lsp plugin crate #1179)
• forc-explore (Move forc's block explorer support into a dedicated forc-explore plugin crate #1180)
• forc-fmt (Move forc's fmt command support into a dedicated forc-fmt plugin crate #1196)

[adlerjohn]

This might help: https://github.com/gakonst/foundry/blob/master/.github/workflows/release.yml

[emilyaherbert]

I'm hoping to use this feature for a workshop during EthCC in mid-July. Would it be possible to have this feature implemented by mid-June? The extra buffer time would be to allow for integration with the workshop layout, etc.

(This question is mostly poised to the void, as there is not currently someone assigned to this issue, CC @sezna @mohammadfawaz )

This issue is related: FuelLabs/fuels-rs#237

[ra0x3]

@mitchmindtree Just FYI this issue description is so wonderful it hurts 🥲 Thanks