[8.x](backport #4318) FIPS compliant builds

[mergify]

What is the problem this PR solves?

Add ability to make FIPS compliant builds when FIPS=true is specified.

How does this PR solve the problem?

Specifying FIPS=true will change the following:

• PLATFORMS will default to linux/amd64 linux/arm64
• make local, make release-* - Binary will be build with -tags=fipsrequired and GOEXPERIMENT=systemcrypto
• make build-releaser - chaingaurd microsoft go image will be used as base
• make multipass - microsoft's go toolchain will be downloaded and installed to VM

How to test this PR locally

Design Checklist

• I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
• I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
• I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool

Related issues

---

This is an automatic backport of pull request #4318 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of f1c29b9 has failed:

On branch mergify/bp/8.x/pr-4318
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit f1c29b9.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .buildkite/scripts/test-release.sh
	new file:   Dockerfile.fips
	new file:   docs/fips.md

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   Makefile
	both modified:   dev-tools/multipass-cloud-init.yml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mergify]

This pull request has not been merged yet. Could you please review and merge it @michel-laterman? 🙏

[pkoutsovasilis]

@michel-laterman could please take of the git conflicts? 🙂

[elastic-sonarqube]

Quality Gate failed

Failed conditions
4 Security Hotspots

See analysis details on SonarQube