Convert Makefile to magefile.go

[michel-laterman]

What is the problem this PR solves?

The Makefile has reached a point where it is becoming difficult to understand and add new features/targets.

How does this PR solve the problem?

Reimplement Makefile targets in mage.
Change buildkite pipeline to use mage.
Change Dockerfile* to use mage.

Added bonuses:

• Support for producing NOTICE-FIPS.txt
  • NOTICE files only contain modules used in shipped binaries.
• cloudE2E testing is functional
• Minor increase in parallel execution for targets.
• env only settings controls
  • target doc strings contain env var usage info
• conditional linter installation
• integration/e2e test token reuse
• improved release testing (archive structure, non-zero len binaries, fips capable indicators if FIPS=true)
• reimplemented bash scripts in dev-tools for mage, removed unused scripts.

How to test this PR locally

mage -l

See doc strings for targets with mage -h TARGET i.e.:

mage -h build:binary
Binary builds release binaries for the specified platforms. PLATFORMS may be used to set os/arch for compiled binaries. DEV creates a development build. SNAPSHOT creates a snapshot build. FIPS creates a FIPS capable binary. VERSION_QUALIFIER may be used to manually specify a version qualifer for the produced binary.

Usage:

	mage build:binary

[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.

[prodsecmachine]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[michel-laterman]

I wasn't able to get some targets that use docker working locally, specifically:

• docker:binary
• docker:cover
• docker:release

I also did not have the time to verify test:e2e or ~test:cloudE2E~.

EDIT: docker:* targets worked, the issue was that the docker container would oom when building all artifacts in parallel; to fix this i made them build serially.
test:e2e also works.
test:cloudE2E works in buildkite now!

[mergify]

This pull request is now in conflicts. Could you fix it @michel-laterman? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b magefile upstream/magefile
git merge upstream/main
git push upstream magefile

[michalpristas]

looks like some notice conflicts that needs to be solved. other than that looks good

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
1 Fixed issue
0 Accepted issues

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

See analysis details on SonarQube