Use golang-crossbuild as base image

[joshdover]

What is the problem this PR solves?

Use same base image for building Fleet Server as Elastic Agent from https://github.com/elastic/golang-crossbuild

Checklist

• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-04-28T15:42:15.663+0000

• Duration: 19 min 49 sec

Test stats 🧪

Test	Results
Failed	0
Passed	679
Skipped	1
Total	680

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[joshdover]

@michel-laterman @v1v any recommendations on how to test this to make sure this doesn't break anything?

[v1v]

Artifacts are uploaded to a Google bucket:

gsutil list -l gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219
   8019194  2023-02-13T16:18:43Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-darwin-aarch64.tar.gz
       171  2023-02-13T16:18:42Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-darwin-aarch64.tar.gz.sha512
   8504876  2023-02-13T16:18:43Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-darwin-x86_64.tar.gz
       170  2023-02-13T16:18:42Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-darwin-x86_64.tar.gz.sha512
   8047778  2023-02-13T16:18:42Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-linux-arm64.tar.gz
       168  2023-02-13T16:18:42Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-linux-arm64.tar.gz.sha512
   7690550  2023-02-13T16:18:43Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-linux-x86.tar.gz
       166  2023-02-13T16:18:42Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-linux-x86.tar.gz.sha512
   8760745  2023-02-13T16:18:43Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-linux-x86_64.tar.gz
       169  2023-02-13T16:18:42Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-linux-x86_64.tar.gz.sha512
   7859618  2023-02-13T16:18:43Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-windows-x86.zip
       165  2023-02-13T16:18:42Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-windows-x86.zip.sha512
   8177708  2023-02-13T16:18:43Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-windows-x86_64.zip
       168  2023-02-13T16:18:42Z  gs://fleet-ci-artifacts/fleet-server/commits/68e1662bf74ff3fa0799e8c81f7a4778d6013219/fleet-server-8.8.0-windows-x86_64.zip.sha512

In addition, I've just found the release ran some release-test verification:

• https://fleet-ci.elastic.co/blue/organizations/jenkins/fleet-server%2Ffleet-server-mbp%2FPR-2339/detail/PR-2339/4/pipeline/272#step-347-log-1

I guess you could download those binaries and start the Fleet-Server, though I'm not much familiar with the Fleet Server itself

[joshdover]

@v1v thank you, we will need to check that.

We also need to check if there are any regressions in this change that were solved by the builder image added in #756

[joshdover]

@michel-laterman @jen-huang Can we prioritize this soon? We need to test these artifacts. We may get lucky and the artifiacts may have the same hashes compared to main. If so, I think we could merge this now.

[michel-laterman]

lgtm; i don't think this should break anything.
Do we want to add a release note for this?