[DO NOT MERGE]

Description

There are currently inconsistencies between the UI test results in CI and those run locally in DDEV — particularly around font rendering (e.g., anti-aliasing, subpixel differences).

This change addresses two key issues:

1. Font rendering parity
   It introduces system-level fontconfig settings to ensure consistent anti-aliasing and subpixel rendering between CI and DDEV.

2. Consistent Chromium version
   It forces the use of Puppeteer v8’s bundled Chromium (revision 856583), which matches what CI runs.

Additionally, this update sets the architecture to linux/amd64 to ensure Puppeteer can install and run the correct Chromium binary. Newer versions of Puppeteer support arm64, but v8 does not.

For Apple Silicon Users

If you're using a Mac with Apple Silicon (M1/M2):

• Make sure Rosetta is enabled in Docker Desktop → Settings → Features in development → Use Rosetta for x86/amd64 emulation on Apple Silicon. This will improve the emulation performance.

Known Issue: Node Architecture Mismatch

On Apple Silicon, Docker may pull a version of Node.js that does not match the forced amd64 platform. If Puppeteer fails to run or Chromium won’t launch, run the following inside the container:

ddev ssh

sudo apt-get purge -y nodejs npm
sudo rm -rf /usr/local/bin/node /usr/local/bin/npm ~/.n
sudo apt-get update
curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash -
sudo apt-get install -y nodejs
hash -r

This installs an amd64-compatible Node.js build that matches the Puppeteer/Chromium environment.

Notes

Some UI tests still fail, but font rendering is now significantly more consistent across environments.

This lays the groundwork for further snapshot cleanup or visual regression stabilization.

Review

• Functional review done
• Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
• Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
• Security review done
• Wording review done
• Code review done
• Tests were added if useful/possible
• Reviewed for breaking changes
• Developer changelog updated if needed
• Documentation added if needed
• Existing documentation updated if needed