Add DRA FIPS artifacts to package pipeline

[michel-laterman]

What is the problem this PR solves?

Provide FIPS dra artifacts.

How does this PR solve the problem?

Add FIPS="true" env flag to packageing pipeline.
Packaging pipline uses microsoft/go instead of golang/go to build DRA artifacts for FIPS.
Change package name from fleet-server-*-fips to fleet-server-fips-*.

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

[mergify]

This pull request does not have a backport label. Could you fix it @michel-laterman? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[jlind23]

@michel-laterman please do not merge https://github.com/elastic/infra/pull/42160 before this gets merged/backported or you'll block the unified release. The same happened to @pchila

[pchila]

@michel-laterman could you please test this PR on buildkite to see if all the artifacts are correctly generated?
Use fleet-server-package-mbp pipeline with:

BRANCH="main"
BUILDKITE_PULL_REQUEST="true"

ref. .buildkite/scripts/dra_release.sh

[michel-laterman]

FIPS DRA attempt: https://buildkite.com/elastic/fleet-server-package-mbp/builds/1739

[michel-laterman]

Currently the FIPS dra is failing as the package step uses make release, however we need to use the microsoft/go toolchain in order to build a FIPS compliant artifact. I'll add this in, I'll copy the with_msft_go (common.sh) command I've added into another PR to resolve this

[michel-laterman]

The FIPS artifact builds are now completing, however it is havin issues authenticating with GCP at the end to upload
.buildkite/scripts/common.sh: line 112: PRIVATE_CI_GCS_CREDENTIALS_SECRET: unbound variable
https://buildkite.com/elastic/fleet-server-package-mbp/builds/1743

My next commit fixed this issue, successful build available: https://buildkite.com/elastic/fleet-server-package-mbp/builds/1744

[michel-laterman]

This is actually a bit of a mess at the moment.
PACKAGES is unused by the Makefile.

Also PLATFORMS is never exported here so it does not get used by the Makefile; both the arm64 and and amd64 instances build all packages.

Should we remove this part entirely, or do we want to restrict the packages each builder should produce?

[michel-laterman]

Thanks a @v1v I changed all our FIPS var checks to use false as a default

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube