Navigation: Prepare for hard deprecation

[mirka]

What?

Starts logging a deprecation warning for Navigation, with an explicit end version.

Why?

After passive deprecating (#61099) this component, we have had to do maintenance work on it many times. Given the low usage, I think it would be beneficial to eventually hard remove this code from the codebase.

Testing Instructions

✅ Deprecation warning should be logged in the Storybook.
✅ Unit tests should pass.

✍️ Dev Note

The Navigation component (and all its subcomponents) are deprecated, planned for hard removal in WordPress 7.1. Use the Navigator component instead.

[github-actions]

Flaky tests detected in 6c8070a.
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/12423238384
📝 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
• [Flaky Test] submenu click on the arrow interactions #61884 in /test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js

[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: ciampo <[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.

[ciampo]

Should we add JS doc @deprecated comments here, similarly to what we've done for other components?

[tyxla]

I think we can also add a README callout as we do for other hard deprecated components:

<div class="callout callout-alert">
This component is deprecated.
</div>

[tyxla]

LGTM 👍

Thanks for writing a dev note proactively 🌟

[mirka]

Should we add JS doc @deprecated comments here, similarly to what we've done for other components?

They were marked in the source files when we first passive deprecated them. It should already be working as expected:

I think we can also add a README callout as we do for other hard deprecated components:

Also already done when we passive deprecated it 👍