Description

The navigation editor seems to make a malformed request for menu items resulting in a 400 status HTTP response:

This seems to be caused by the preceding request for a menu and menu id not being resolved yet. The menu id is needed as a param in the request that's failing.

It seems like an easy enough fix to return early from the resolver for fetching menu items, since this whole process is repeated and completes successfully once a menu id is known.

I've also had to push some fixes for the isPending state of the editor, as otherwise the loading state shows forever when there are no menus with this change. This is already previously buggy, #28124 covers a proper fix.

How has this been tested?

1. Open dev tools on the network tab
2. Open the navigation screen.
3. If there are no menus, create one with some menu items and reload
4. Check network requests, there should be no failed requests
5. Menus should load correctly (including menu items.)

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• 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.