Fix docker cross-platform builds

[bitwiseguy]

The docker images being pushed to docker registry by our CI do not work on arm64 machines. This PR attempts to fix that.

Fixes #11081

Key change to fix cross compiling issues

Removed TARGETOS and TARGETARCH declarations from the top of the dockerfile. These args both get set automatically by the docker build kit, and the global declarations in the dockerfile caused an issue where the values were not set or passed to the underlying make commands which invoke go build.

Additional context

Also added CGO_ENABLED=0 to docker images that are being built for cross-platform. This will cause the build to fail if C code is included in the go source code. This seems better than allowing the build to pass and only catching the failure further downstream when the image is pulled and attempted to run on an arm64 machine. If we want the cross-platform builds to work with C code included, we will have to spend some more effort adding appropriate CC and CXX packages to our docker builder, then allow CGO_ENABLED=1. I'm open to removing this part if reviewers feel this is a bad idea

Tests

Added check-cross-platform ci jobs for every image published during scheduled-docker-publish that is built for multiple platforms (i.e. platforms: "linux/amd64,linux/arm64" for the docker-build job)

[fanbsb]

Please give priority to this PR, we need the arm64 image before the hardfork on op-node 1.7.7

[fanbsb]

This PR works on M1 Mac, but not on AWS Graviton instance.

Error Message
/ # op-node --help
/usr/local/bin/op-node: line 2: syntax error: unexpected "(

[semgrep-app]

Semgrep found 1 sol-style-malformed-revert finding:

• packages/contracts-bedrock/src/cannon/MIPS.sol
  • L460 - Triage

Malformed revert statement style.

_{Ignore this finding from sol-style-malformed-revert.}

Semgrep found 28 golang_fmt_errorf_no_params findings:

• op-chain-ops/upgrades/l1.go
  • L116 - Triage
  • L120 - Triage
  • L198 - Triage
  • L202 - Triage
  • L282 - Triage
  • L286 - Triage
  • L392 - Triage
  • L396 - Triage
  • L400 - Triage
  • L404 - Triage
  • 17 more - Triage
• op-chain-ops/safe/batch.go
  • L200 - Triage

No fmt.Errorf invocations without fmt arguments allowed

_{Ignore this finding from golang_fmt_errorf_no_params.}

Semgrep found 1 nil-check-after-call finding:

• op-node/p2p/node.go
  • L74-167 - Triage

Potential p2pmetrics nil dereference when NewBandwidthCounter is called

_{Ignore this finding from nil-check-after-call.}

Semgrep found 1 math-random-used finding:

• proxyd/backend.go
  • L12 - Triage

Do not use math/rand. Use crypto/rand instead.

_{Ignore this finding from math-random-used.}

Semgrep found 2 todos_require_linear findings:

• op-e2e/actions/l2_sequencer.go
  • L106 - Triage
• op-conductor/rpc/backend.go
  • L32 - Triage

Please create a GitHub ticket for this TODO.

_{Ignore this finding from todos_require_linear.}

Semgrep found 1 os-error-is-not-exist finding:

• op-chain-ops/cmd/registry-data/main.go
  • L284 - Triage

New code should use errors.Is with the appropriate error type

_{Ignore this finding from os-error-is-not-exist.}

Semgrep found 2 marshal-json-pointer-receiver findings:

• op-chain-ops/safe/batch.go
  • L131 - Triage
  • L274 - Triage

MarshalJSON with a pointer receiver has surprising results: golang/go#22967

_{Ignore this finding from marshal-json-pointer-receiver.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.69%. Comparing base (3eb9861) to head (a231f98).
Report is 17 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop   #10827   +/-   ##
========================================
  Coverage    60.69%   60.69%           
========================================
  Files           20       20           
  Lines         1781     1781           
  Branches        71       71           
========================================
  Hits          1081     1081           
  Misses         667      667           
  Partials        33       33           

Flag	Coverage Δ
cannon-go-tests	79.69% <ø> (ø)
chain-mon-tests	27.14% <ø> (ø)
sdk-tests	16.44% <ø> (ø)

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

[protolambda]

Regarding op-program: the host part is not subject to the same reproduction and platform target restrictions as the client part