Feat: static release ci

[gluax]

Motivation

For the release CI to release statically built binaries and leverage pre-built binaries for release docker images to save CI time.

Explanation of Changes

Updates Dockerfile.static to use go 1.21, which cosmos SDK 0.50 requires.
Removes the Dockerfile.node-static since using a static file in Docker doesn't matter.
Adds a Dockerfile.build-static which compiles the chain statically for both amd and arm.

Modifies the Release pipeline in the following ways:

• Uses the build static docker image to build the binaries. I tried really hard to get statically compiling CGO to work outside of an alpine image. CGO was unhappy no matter what I did, so I gave up.
• Removes goreleaser; unfortunately, it didn't support cross-compiling CGO as far as I could determine.
• Releases the static binaries for amd and arm(linux only).
• Leverages those already-built binaries to release the docker image as well(cuts CI time down to about 8minutes).

Testing

I tested the CI in a forked version and ensured it ran successfully and releases. I tested the binary itself and the docker image as much as possible. However, it failed to join devnet, and I think this is because the binary is the new SDK version.

Related PRs and Issues

Closes #105.
Closes #106.

[hacheigriega]

I guess this will fail once #117 is merged because it involves a private repo?

[gluax]

I guess this will fail once #117 is merged because it involves a private repo?

@hacheigriega most certainly lol. Unless we figure out go pulling a private dep within CI. Same reason the e2e tests prob fail for that branch yea?

[hacheigriega]

I guess this will fail once #117 is merged because it involves a private repo?

@hacheigriega most certainly lol. Unless we figure out go pulling a private dep within CI. Same reason the e2e tests prob fail for that branch yea?

Yep. 🥲