Components: Add missing descriptions for design system components

[aduth]

What?

Adds JSDoc descriptions for all components which are surfaced as design system components through the Storybook manifest file, which in turn are used by the @wordpress/design-system-mcp package.

In doing so, it also fixes missing component props for three components: ColorPicker, DataViews, and Navigator.

Why?

Descriptions are useful in order to understand what a component does and whether it's usage is applicable to a given use-case.

With AI agent workflows leveraging the @wordpress/design-system-mcp, descriptions are a particularly important part of the agent workflow, since an AI agent is instructed to get a list of components via the get_components tools before diving into individual component details with get_component_details. Since the only information surfaced on get_components listing is the component name and description, the description is a pivotal detail to cue an agent to retrieve more information if it would understand it to be relevant for a given request.

How?

Adds missing JSDoc documentation to components.

For a few of these, I had to employ the same workaround as in #77382 to ensure that the docgen tool correctly parses these components, via inline render configuration in the component stories. This should be temporary and may already be resolved upstream. Worth noting that this fixes a preexisting issue with these components props not being surfaced in the manifest (see "3/66 prop type errors" on live components HTML manifest).

Testing Instructions

Verify that built Storybook manifest parses all components successfully and all components have descriptions:

1. Run npm run storybook:build
2. Run open storybook/build/manifests/components.html
3. Observe "66 components okay" (compare to "3/66 prop type errors" on live components HTML manifest)
4. Observe every listed component has a description (compare to live components HTML manifest missing descriptions for affected components like ColorPicker, DataViews, etc.)

Verify that descriptions appear in live Storybook site:

1. Run npm run storybook:dev
2. In the launched Storybook site at http://localhost:50240/, navigate to a Storybook page for one of the affected components (e.g. ColorPicker)
3. Observe that the Storybook shows a description

Screenshots or screencast

Use of AI Tools

Assessment and initial implementation (including descriptions themselves) with Claude Opus 4.8. Manual review and edits of most of the descriptions for readability and conciseness.

[github-actions]

Size Change: 0 B

Total Size: 7.51 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: aduth <aduth@git.wordpress.org>
Co-authored-by: ntsekouras <ntsekouras@git.wordpress.org>
Co-authored-by: ciampo <mciampini@git.wordpress.org>

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

[aduth]

Worth noting that this fixes a preexisting issue with these components props not being surfaced in the manifest (see "3/66 prop type errors" on live components HTML manifest).

Note that I'm actively working on a solution for better detection of this kind of problem through the issue tracked at #79415.

[aduth]

I'm not sure why the CHANGELOG CI check is failing for the theme package 🤔 I'm not touching the theme package.

[aduth]

I'm not sure why the CHANGELOG CI check is failing for the theme package 🤔 I'm not touching the theme package.

Found the issue and fixed separately: #79548

[ciampo]

LGTM 🚀

I don't have further feedback