Navigation: Surface the associated Menu name in the List View tab

[im3dabasia]

Fixes Point 1 of #68177

What?

This PR surfaces the name of the currently selected menu next to the word "Menu" in the Navigation block's List View tab, making it easier for users to identify which menu is associated with the block directly within the editor interface.

Why?

Currently, to identify which menu is linked to a Navigation block, users must navigate through multiple steps:

1. Select the Navigation block,
2. Open the block sidebar,
3. Click on the List View tab,
4. Open the 3-dot menu,
5. See the currently selected menu.

This multi-step process can be cumbersome, especially for less experienced users. This change simplifies this by immediately displaying the menu name alongside the "Menu" label, improving discoverability and usability.

How?

This change uses the useNavigationMenu hook to display the current menu name next to the "Menu" label in the Navigation block's List View tab. The aim is to provide immediate feedback without overloading the UI.

Testing Instructions

1. Open a post or page in the WordPress editor.
2. Insert a Navigation block or select an existing one.
3. Open the block sidebar.
4. Switch to the "List View" tab.
5. Verify that the name of the currently selected menu is displayed next to the "Menu" label.

Screencast

Screen.Recording.2025-01-01.at.1.21.31.PM.mov

[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: im3dabasia <im3dabasia1@git.wordpress.org>
Co-authored-by: yogeshbhutkar <yogeshbhutkar@git.wordpress.org>
Co-authored-by: getdave <get_dave@git.wordpress.org>

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

[yogeshbhutkar]

Thanks for the PR ✨. I've fixed the second point here.

[im3dabasia]

Hi @getdave ,
When you have a moment please could you review my PR

[getdave]

Hi @getdave , When you have a moment please could you review my PR

👋 Unfortunately my availability to contribute to Core is limited so I likely won't get around to this. Looks like @fabiankaegy pinged some folks though so hopefully they can help.

[t-hamano]

Thanks for the PR! Three pieces of feedback from me:

• Navigation name can get long, so we need to consider how it should be displayed.
• We should not hard-code concatenations of localized text - they should all be translatable, like this:

  { sprintf(
  	/* translators: %s: Navigation menu name. */
  	__( 'Menu (%s)' ),
  	navigationMenu?.title || __( 'Untitled menu' )
  ) }

• Let's consider whether we really need to add the menu name here. In this comment, it is suggested to add the menu name to the block card.