ironbank: support for heartbeat

[v1v]

Motivation/summary

Automate the docker context generation for the Heartbeat IronBank releases, this will allow us to move away from creating those docker context manually in a different repository, since the Platform Release team already provide the automation.

Implementation details

1. Support for mage ironbank

DoD build context content

As required the build context contains the following files:

• Dockerfile with specific requirements for DoD (registry args, no internet dependencies, healthcheck, ...)
• hardening_manifest.yaml with all required dependencies
• LICENSE specific for DoD
• README.md with specific content for DoD
• config/ (optional) directory containing all config files to include into the Docker image
• scripts/ directory containing all scripts to include into the Docker image (example: entrypoint...)

Why is it important?

No more manual post-release steps to generate the ironbank releases for heartbeat

Actions

• Generate the ironbank tar.gz docker context following the Unified Release requirements
• Generate hardening_manifest.yaml that includes all the dependencies.

Test

$ mage ironbank
>> prepareIronbankBuild: prepare the IronBank container context.
>> saveIronbank: save the IronBank container context.
>> creating TAR file from directory: build/heartbeat-ironbank-8.5.0-docker-build-context, target: build/distributions/heartbeat-ironbank-8.5.0-docker-build-context.tar.gz
>> skipping root directory
ironbank ran for 22.143145ms

produced

$ tree build/heartbeat-ironbank-8.5.0-docker-build-context 
build/heartbeat-ironbank-8.5.0-docker-build-context
├── Dockerfile
├── LICENSE
├── README.md
├── hardening_manifest.yaml
└── signatures
    ├── RPM-GPG-KEY-CentOS-Official
    ├── RPM-GPG-KEY-rockyofficial
    └── linux_signing_key.pub

1 directory, 7 files
$ grep -R 8.5.0 build/heartbeat-ironbank-8.5.0-docker-build-context
build/heartbeat-ironbank-8.5.0-docker-build-context/Dockerfile:ARG ELASTIC_STACK=8.5.0
build/heartbeat-ironbank-8.5.0-docker-build-context/README.md:[here](https://www.elastic.co/guide/en/beats/libbeat/current/release-notes-8.5.0.html).
build/heartbeat-ironbank-8.5.0-docker-build-context/hardening_manifest.yaml:  - "8.5.0"
build/heartbeat-ironbank-8.5.0-docker-build-context/hardening_manifest.yaml:  ELASTIC_STACK: "8.5.0"
build/heartbeat-ironbank-8.5.0-docker-build-context/hardening_manifest.yaml:  org.opencontainers.image.version: "8.5.0"
build/heartbeat-ironbank-8.5.0-docker-build-context/hardening_manifest.yaml:  - filename: "heartbeat-8.5.0-linux-x86_64.tar.gz"
build/heartbeat-ironbank-8.5.0-docker-build-context/hardening_manifest.yaml:    url: "<artifact_path>/heartbeat-8.5.0-linux-x86_64.tar.gz"
build/heartbeat-ironbank-8.5.0-docker-build-context/hardening_manifest.yaml:      value: e327d8469bd71ea0d747673bc362240e3ddad672a0eb7fe815a06d1317e74598

Issues

A similar approach was done for other beats.

It also contains the fix put in place in #32867 but for heartbeats

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @v1v? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[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: 2022-09-01T10:57:00.212+0000

• Duration: 142 min 4 sec

Test stats 🧪

Test	Results
Failed	0
Passed	22747
Skipped	1947
Total	24694

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[v1v]

➜  /tmp gsutil cp gs://beats-ci-artifacts/beats/pull-requests/pr-32954/heartbeat/heartbeat-ironbank-8.5.0-SNAPSHOT-docker-build-context.tar.gz . 
Copying gs://beats-ci-artifacts/beats/pull-requests/pr-32954/heartbeat/heartbeat-ironbank-8.5.0-SNAPSHOT-docker-build-context.tar.gz...
/ [1 files][ 25.7 KiB/ 25.7 KiB]                                                
Operation completed over 1 objects/25.7 KiB.                                     
➜  /tmp tar -xvf heartbeat-ironbank-8.5.0-SNAPSHOT-docker-build-context.tar.gz 
x Dockerfile
x LICENSE
x README.md
x hardening_manifest.yaml
x signatures
x signatures/RPM-GPG-KEY-CentOS-Official
x signatures/RPM-GPG-KEY-rockyofficial
x signatures/linux_signing_key.pub
➜  /tmp grep 8.5.0 *
Dockerfile:ARG ELASTIC_STACK=8.5.0
README.md:[here](https://www.elastic.co/guide/en/beats/libbeat/current/release-notes-8.5.0.html).
hardening_manifest.yaml:  - "8.5.0"
hardening_manifest.yaml:  ELASTIC_STACK: "8.5.0"
hardening_manifest.yaml:  org.opencontainers.image.version: "8.5.0"
hardening_manifest.yaml:  - filename: "heartbeat-8.5.0-linux-x86_64.tar.gz"
hardening_manifest.yaml:    url: "<artifact_path>/heartbeat-8.5.0-linux-x86_64.tar.gz"
hardening_manifest.yaml:      value: e327d8469bd71ea0d747673bc362240e3ddad672a0eb7fe815a06d1317e74598