Site Editor: Add E2E coverage for view config extensibility

[jorgefilipecosta]

What?

Follow-up to #80319.

Adds end-to-end coverage for extending the Pages view configuration in the Site Editor. The test covers all four configuration mutation methods (merge, remove, set, and replace) and the four UI-facing configuration areas: the default view, available views, layouts, and Quick Edit form.

Why?

The view configuration API did not have a browser test proving that changes made through get_entity_view_config_postType_page travel through the REST API and affect the Site Editor UI.

How?

• Adds a test-only plugin that modifies Core's existing Pages configuration.
• Retitles and filters an existing view, removes the Scheduled view, and adds a new Published after 2020 view with locked status and date filters.
• Configures the default table sorting and fields, restricts layouts to table with a custom Status column width, and changes the Quick Edit form layout and fields.
• Seeds matching and nonmatching pages, navigates the complete Site Editor UI path, and verifies the records shown by the existing and newly added views.

Testing Instructions

1. Start the E2E environment.

2. Run:

   npm run test:e2e -- test/e2e/specs/site-editor/view-config-extensibility.spec.js --project=chromium

The focused Chromium test should pass.

Testing Instructions for Keyboard

Not applicable. This PR only adds automated test coverage and a test-only plugin; it does not change production UI behavior.

Screenshots or screencast

Custom filtered view

The new Published after 2020 view exposes its locked date and status filters and displays only the matching page.

Customized Quick Edit form

The filtered form uses the regular layout and exposes only the Link field.

Use of AI Tools

OpenAI Codex was used to inspect the relevant API and prior E2E review feedback, implement the test coverage, and run the verification steps. The changes were reviewed and refined interactively by the author.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Required label: Any label starting with [Type].
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[github-actions]

Size Change: 0 B

Total Size: 7.75 MB

_{compressed-size-action}

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jorgefilipecosta <jorgefilipecosta@git.wordpress.org>
Co-authored-by: oandregal <oandregal@git.wordpress.org>
Co-authored-by: shail-mehta <shailu25@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[shail-mehta]

@jorgefilipecosta Apologies, I accidentally updated the branch.🙏

[github-actions]

Flaky tests detected in ff02916.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/29939525616
📝 Reported issues:

• [Flaky Test] should allow user to add and remove multiple local font files #78760 in /test/e2e/specs/admin/font-library.spec.js

[jorgefilipecosta]

@jorgefilipecosta Apologies, I accidentally updated the branch.🙏

No problem @shail-mehta ☺️

[oandregal]

This is a great initiative, thanks!