Navigation: Soft deprecate component

[mirka]

What?

Soft deprecates the Navigation component, to discourage new usage and to signal that it is in maintenance mode.

Why?

Usage of the Navigation component has been dropped in Gutenberg in favor of Navigator. We don't think a lot of extenders are using this component, and it's unlikely that we'll do any dev work on it anymore. @ciampo and I agreed that we should deprecate it.

[github-actions]

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

• [Flaky Test] default to the only existing classic menu if there are no block menus #48033 in /test/e2e/specs/editor/blocks/navigation.spec.js

[mirka]

We can add components to this list as we remove their experimental status (#59418), and once all of them are done we can simplify to a bulk redirect on components-experimental- prefixes.

More info on the redirect mechanism at #59181.

[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: mirka <[email protected]>
Co-authored-by: tyxla <[email protected]>

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

[tyxla]

Looks good 👍 Thanks!