Ensure that builds are deterministic and enforce with tests

[kristovatlas]

Description

Ideally, the build process for Gno should be fully deterministic such that all binaries built for the same target platform produce the same sha-256 hash.

Deterministic builds ensure that a given source code always produces the same binary output, regardless of external factors like build environment or timing. This reduces the risk of introducing hidden vulnerabilities, as developers can verify the integrity and authenticity of the build. It also makes it easier to track changes, reproduce builds for auditing, and prevent supply chain attacks where malicious modifications might go undetected in the build process.

If this not already the case, once we achieve this milestone, it should be enforced in the CI/CD pipeline to prevent regression.

Reference: https://go.dev/blog/rebuild