build: cross compile darwin builds

[DanStough]

Description

For cost reasons, we can cross-compile macos binaries on linux. Historically we didn't do this because of a problem with Go that has since been resolved: #3267.

This step removes the verification of Darwin binaries. I believe this is acceptable since the vast majority of users and on Linux and Windows. Developers will naturally test the Darwin build during the development cycle.

[jm96441n]

quick question: what does the verify step actually do? nvm, read the script and it just checks the version of the binary and all that, I wasn't sure if it did anything related to signing binaries for macos

[DanStough]

Yeah, CRT does the binary signing. Sounds like this verify step wouldn't have caught the previous DNS issue anyway since it is only checking the version.

[hc-github-team-consul-core]

@DanStough, a backport is missing for this PR [21326] for versions [1.15] please perform the backport manually and add the following snippet to your backport PR description:

<details>
	<summary> Overview of commits </summary>
		- <<backport commit 1>>
		- <<backport commit 2>>
		...
</details>

[hc-github-team-consul-core]

@DanStough, a backport is missing for this PR [21326] for versions [1.15] please perform the backport manually and add the following snippet to your backport PR description:

<details>
	<summary> Overview of commits </summary>
		- <<backport commit 1>>
		- <<backport commit 2>>
		...
</details>