e2e-commons: match editor panel name exactly to unblock post-editor e2e

[CGastrell]

Fixes the strict-mode violation currently breaking the Jetpack post editor e2e tests check on every PR (e.g. #49099, #49100, #49104).

Proposed changes

• In tools/e2e-commons/pages/editor-page.ts, the openSettings() helper opens the editor's More menu and looks up the target panel toggle with getByRole( 'menuitemcheckbox', { name: target } ). Playwright's name does a substring match by default, so openSettings( 'Jetpack' ) resolves to both the "Jetpack" panel and the "Jetpack Newsletter" panel (registered at extensions/blocks/subscriptions/menu.js:42).
• Result: strict-mode violation → sidebar-social.test.ts fails before it can even open the sidebar.
• Fix: pass exact: true so the matcher requires name === target.

Why this only started failing now

The Newsletter panel has existed since #47857 (March), but it's only visible when the subscriptions module is active. #49034 (merged 2026-05-22 14:42 UTC) flipped subscriptions on by default, which is when the Jetpack post editor e2e job started failing on every subsequent PR.

Timeline:

• PR Connection: dynamic logo and tooltip in users list #49093 ran at 12:43 UTC → passes (pre-Newsletter: enable the subscriptions module by default #49034)
• PR ActivityPub: Widen Reader auth shim to user-actor routes #49100 (15:05), classic-theme-helper: Add notice that Custom Content Types are primarily for classic themes #49104 (17:27), Connection: migrate ActionButton, Button, and Text to @wordpress/ui #49099 (19:02) → all fail with the same strict-mode violation on the same selector

Testing instructions

• Re-run the Jetpack post editor e2e tests job for this PR — it should pass.
• Once merged, rebasing any of the currently-broken PRs (Connection: migrate ActionButton, Button, and Text to @wordpress/ui #49099, ActivityPub: Widen Reader auth shim to user-actor routes #49100, classic-theme-helper: Add notice that Custom Content Types are primarily for classic themes #49104) will unblock their e2e check too.

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

No.

[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 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!