View Config: add reference docs

[oandregal]

What?

Updates the documentation for the view config API.

Why?

To have a single place of reference.

How?

Creates a reference doc for the view config API, similar to the theme.json one.

Testing Instructions

• Read the docs.
• Verify the document is live after merging the PR.

[Copilot]

Pull request overview

Adds centralized reference documentation for the View Configuration API.

Changes:

• Documents configuration properties, filters, and mutation methods.
• Registers the reference in documentation navigation.
• Removes duplicated guidance from the filters guide.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
docs/toc.json	Adds the reference to the table of contents.
docs/manifest.json	Registers the published documentation page.
docs/reference-guides/view-config-reference.md	Introduces the API reference and examples.
docs/how-to-guides/curating-the-editor-experience/filters-and-hooks.md	Removes duplicated View Configuration documentation.

Suppressed comments (2)

docs/reference-guides/view-config-reference.md:55

• activity is listed as a supported layout immediately above and in the REST schema, but its configuration entry is absent from this table.

| list | View overrides applied when the list layout is selected. | `object` |

docs/reference-guides/view-config-reference.md:129

• This purported list omits the supported description field and details layout, both of which are accepted by the REST schema (class-gutenberg-rest-view-config-controller-7-1.php:739-750,768-777).

| label | Label displayed for the field, overriding the field's own. | `string` |
| layout | How the field is rendered: `type` is one of `regular`, `panel`, `card`, or `row`, and `labelPosition` is one of `side`, `top`, or `none`. | `{ type, labelPosition }` |
| children | Fields combined under this entry, following the same shape as `fields`. | `[ string \| object ]` |

[oandregal]

My goal with this PR is to bootstrap a place to document this, it doesn't aim to be comprehensive at this stage. I'll follow up by investigating how this document can be maintained up to date automatically based on the REST endpoint schema (and that point, we do want to be comprehensive).

[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: oandregal <oandregal@git.wordpress.org>

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

[oandregal]

@t-hamano I've tagged this to backport based on the latest conversations. I'll backport manually if the process fails.

Even though it's new documentation (plus a link in existing docs), I assume it's something we want to have in the 7.1 branch for local documentation purposes (the handbook is built based on trukn AFAIK).

[github-actions]

I just cherry-picked this PR to the wp/7.1 branch to get it included in the next release: 69969a0