Navigation screen: On mobile viewports, reveal the block inspector when clicking the menu name button

[getsource]

Description

Opens Block Inspector when menu name is clicked.

Worked on this with @Mamaduka. Thanks!

Closes: #30326

How has this been tested?

Tested in wp-env and responsive/mobile viewport within dev tools in Firefox.
From #30326:

• Open the nav editor and switch to a mobile viewport
• Ensure the block inspector is hidden
• Select the nav block
• Click the menu name button

Also, ran npm run test, and it passed as expected.

Screenshots

Types of changes

Bug fix.

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR (please manually search all *.native.js files for terms that need renaming or removal).

[getsource]

Just rebased this.
@draganescu Here are before and after videos to help with any design feedback necessary.

Essentially, it doesn't do anything on tap/click in mobile viewports before this change, and afterwards, it opens the block inspector and moves focus so the name can be modified, to match the behavior when the block inspector is already visible.

Before:

Screen.Recording.2021-05-12.at.20.24.49.mp4

After:

Screen.Recording.2021-05-12.at.20.23.27.mp4

[getdave]

Screen.Capture.on.2021-05-13.at.11-53-14.mov

Thank you for this PR. It works really well and solves the issue well.

One thing that we might want to create a follow up Issue for is that (on "mobile") once you have edited the Menu name it is not clear where to persist that change. This is because you have to close the inspector to be able to see the Save button.

I wonder whether we should also show the Save button at the top of the inspector on smaller viewports where the inspector takes over the entire screen?

[getsource]

Thanks much @getdave @Mamaduka !

I agree improving the flow would be good. Do you think it'd be better to include that sort of a change with #31241 (H/T to @Mamaduka for pointing this one out), or track it in a new/separate issue?