fix(synthetics): chromium dependencies for Synthetics monitor

[mcapell]

Proposed commit message

Add missing dependency to run chromium on wolfi images.

Checklist

• My code follows the style guidelines of this project
  - [ ] 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
  - [x] I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Within the ./x-pack/heartbeat directory, build the docker image with:

DEV=true PLATFORMS=linux/arm64 PACKAGES=docker mage package

Without the dependency, the build fails with the following error:

Dockerfile:129
--------------------
 128 |     RUN (npm i -g --loglevel verbose --production --engine-strict  @elastic/synthetics@stack_release || sh -c 'tail -n +1 ${NPM_CONFIG_PREFIX}/_logs/* && exit 1')
 129 | >>> RUN CHROMIUM_BIN=$(ls -1 /usr/share/heartbeat/.cache/ms-playwright/chromium_headless_shell-*/chrome-linux/headless_shell | head -n1);\
 130 | >>>     $CHROMIUM_BIN --version
 131 |
--------------------
ERROR: failed to build: failed to solve: process "/bin/sh -c CHROMIUM_BIN=$(ls -1 /usr/share/heartbeat/.cache/ms-playwright/chromium_headless_shell-*/chrome-linux/headless_shell | head -n1);    $CHROMIUM_BIN --version" did no
t complete successfully: exit code: 127

Related issues

Use cases

Screenshots

Logs

[github-actions]

🤖 GitHub comments

Just comment with:

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

[elasticmachine]

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mcapell? 🙏.
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-8./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.

[github-actions]

@Mergifyio backport 8.19 9.2 9.3

[mergify]

backport 8.19 9.2 9.3

✅ Backports have been created

Details

• #48597 [8.19](backport #48569) fix(synthetics): chromium dependencies for Synthetics monitor has been created for branch 8.19
• #48598 [9.2](backport #48569) fix(synthetics): chromium dependencies for Synthetics monitor has been created for branch 9.2
• #48599 [9.3](backport #48569) fix(synthetics): chromium dependencies for Synthetics monitor has been created for branch 9.3