super-cache: Fix E2E tests

[anomiex]

Proposed changes:

• Update MariaDB image health check for v11 images.
• Update container ID detection for docker-compose v2.
• Pass Accept: text/html in requests for WP Super Cache - add support for the Accept HTTP header #29456. (Axios by default passes application/json, text/plain, */*).

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

None.

Does this pull request change what data or activity we track or use?

No

Testing instructions:

• Try running the tests.

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Super Cache plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[anomiex]

I ran into these failing when testing for whether #43808 would break the tests if we pnpmfile-hack the dependency instead of waiting for kulshekhar/ts-jest#4891 or keeping jest v29 here.

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report

[tbradsha]

In trunk I couldn't env:up, probably related:

 ✔ wordpress                              Built                            0.0s 
 ✔ Network super-cache-e2e_default        Created                          0.0s 
 ✔ Volume "super-cache-e2e_db_data"       Created                          0.0s 
 ✔ Volume "super-cache-e2e_wp_data"       Created                          0.0s 
 ✘ Container super-cache-e2e-db-1         Error                          101.2s 
 ✔ Container super-cache-e2e-wordpress-1  Created                          0.0s 
dependency failed to start: container super-cache-e2e-db-1 is unhealthy
 ELIFECYCLE  Command failed with exit code 1.

This branch spins up the image and runs the tests successfully.

I am curious why this didn't come up before. The last run I see related to super-cache skipped the E2E tests altogether (is this something we want):
https://github.com/Automattic/jetpack/actions/runs/15542181460/job/43755327828

[anomiex]

In trunk I couldn't env:up, probably related:

Yeah, the "Update MariaDB image health check for v11 images" is needed to fix that. The Docker MariaDB image stopped including mysqladmin, it only has mariadb-admin now.

I am curious why this didn't come up before. The last run I see related to super-cache skipped the E2E tests altogether

As far as I can tell, no one ever got around to adding these into CI. They're intentionally not using the tools/e2e-commons stuff, and maybe even aren't really "E2E" tests in the sense of our other E2Es.