Tabs: add docs about not recommending usage with links

[ciampo]

What?

Following the conversation in #67699, this PR introduces a section in the Tabs component's README about discouraging the usage of the component with links.

Why?

See #67699 (comment)

How?

Added a section to the README

Testing Instructions

Read the added docs

[ciampo]

@WordPress/gutenberg-components do you think that a section in the README is enough? Would you also add some extra docs to Storybook, and in what shape?

And finally, what is the plan once we switch to auto-generating the README? Should we have an additional "best practices" Storybook doc, like we're doing with Button ?

[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: ciampo <mciampini@git.wordpress.org>
Co-authored-by: tyxla <tyxla@git.wordpress.org>
Co-authored-by: mirka <0mirka00@git.wordpress.org>

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

[github-actions]

Flaky tests detected in eab9126.
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/12432874889
📝 Reported issues:

• [Flaky Test] Navigates the items list via UP/DOWN arrow keys #64334 in /test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js

[tyxla]

@WordPress/gutenberg-components do you think that a section in the README is enough? Would you also add some extra docs to Storybook, and in what shape?

I think it's more than enough. Listing all possible ways people can use any component is a hard job, but it's nice we're trying 😅

And finally, what is the plan once we switch to auto-generating the README? Should we have an additional "best practices" Storybook doc, like we're doing with Button ?

Using auto-generated docs could be definitely documented as a separate point in the component contribution guidelines.

[tyxla]

👍

[mirka]

@WordPress/gutenberg-components do you think that a section in the README is enough? Would you also add some extra docs to Storybook, and in what shape?

And finally, what is the plan once we switch to auto-generating the README? Should we have an additional "best practices" Storybook doc, like we're doing with Button ?

We might as well do that conversion now: #68209

Feel free to push these content changes into the Best Practices page in that PR. Or you can open a new PR after it lands, if you prefer.

[ciampo]

Sounds good! Closing this PR in favour of #68209, to which I pushed a commit adding a "tabs with links" section