Update wordpress Docker tag to v7

[matticbot]

This PR contains the following updates:

Package	Update	Change
wordpress	major	6.9-php8.2-apache → 7.0-php8.2-apache

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 02:59 AM, on day 1 of the month ( * 0-2 1 * * ) in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[anomiex]

@LiamSarsfield Any reason not to do this? I don't know how to test it.

[LiamSarsfield]

@anomiex Good to merge. This bumps the WordPress image the perf/CodeVitals harness renders against tools/performance/

I ran the suite on 6.9 vs 7.0, 5 iterations each. The wp-admin Dashboard scenario held steady: LCP 132→132ms, FCP 132→132ms, TTFB 52→53ms. So no baseline shift in CodeVitals from the bump. The "Forms responses" scenario times out on both 6.9 and 7.0, which is the known FORMS-728 issue (fix in #50453), not this PR.

To test locally:

pnpm install
cd tools/performance
pnpm setup:browsers
node scripts/run-performance-tests.js --skip-codevitals

Needs Docker and Node ≥20. The first run clones the pre-built plugin from the jetpack-production mirror and installs WordPress, so give it a few minutes. Then check the Jetpack (connected sim) line in the summary: a median LCP around 130ms means 7.0 booted and rendered fine. That's the smoke test.

Ignore the Forms responses ... FAILED line and the non-zero exit, they're the FORMS-728 issue above. Tear down with pnpm run docker:down.

[anomiex]

Next time, feel free to merge it yourself once you've reviewed. 🙂 Renovate is an automated update tool, it won't merge itself.