This change treats Navigation blocks like Template Parts in Write Mode by giving them 'contentOnly' editing mode when outside of sections.

This allows Navigation blocks to be selectable and editable in Write Mode while maintaining the content-focused editing experience, similar to how Template Parts work.

…panel

- Modified block inspector logic to show Navigation block controls when selected
- Added condition to check for 'core/navigation' block type
- Ensures Navigation block inspector is shown instead of parent section block
- Enables direct access to Navigation block's List View tab from Content panel

- Import chevronRight icon from @wordpress/icons
- Add blockName detection to BlockQuickNavigationItem
- Show chevron icon only for 'core/navigation' blocks
- Provides visual indication that Navigation blocks have click-through behavior

- Add logic to detect when Navigation block is in contentOnly mode
- When in contentOnly mode, back button targets parent section instead of parent Navigation block
- Use getParentSectionBlock() to find the nearest section block
- Maintain existing behavior for other Navigation block contexts
- Improves navigation flow when editing Navigation blocks from Content panel

- Add buttonLabel logic to useSelect hook
- When in contentOnly mode: 'Go to parent section'
- When in normal mode: 'Go to parent Navigation block'
- Use dynamic buttonLabel in Button component
- Provides clear context about where the back button will navigate

…logic to check if current block is a child of a Navigation block\n- Use getBlockParentsByBlockName to find Navigation block parents\n- Force blockEditingMode to 'disabled' for Navigation block children\n- Ensures child blocks of Navigation blocks cannot be edited directly\n- Maintains existing editing behavior for all other blocks

This is a prototype hack to prevent direct editing of Navigation block children
while still allowing them to be selectable and managed through the Navigation
block's List View interface.

## What this hack does:

1. **Detection**: Uses getBlockParentsByBlockName() to check if the current
   block has any 'core/navigation' block parents

2. **Override**: If a block is a child of a Navigation block, forces its
   blockEditingMode to 'disabled' regardless of other editing mode logic

3. **UI Control**: Updates multiple properties to respect the disabled state:
   - blockEditingMode: Set to 'disabled' for Navigation children
   - isSubtreeDisabled: Disables the entire subtree
   - isEditingDisabled: Prevents editing interactions
   - hasEditableOutline: Removes editable outline styling
   - mayDisplayControls: Hides editing controls

## Why this hack is needed:

The Navigation block's child blocks (navigation links, submenus) have
role: 'content' attributes which would normally make them editable in
Write Mode. However, for the Navigation block UX, we want these children
to be managed through the Navigation block's List View interface rather
than being directly editable in the canvas.

## Limitations:

- This is a prototype solution that may need refinement
- Only affects direct children of Navigation blocks
- May need additional logic for deeper nesting scenarios
- Could be replaced with a more elegant solution in the future

…al on contentOnly mode

- Add Edit navigation button to Template Part blocks when Navigation blocks are present
- Button only shows in contentOnly mode and selects first Navigation block
- Disambiguate button labels: Edit template part vs Edit navigation
- Update Navigation block Edit button to use sentence case for consistency
- Fix enableComplementaryArea import from interfaceStore

- Change button label from 'Edit template part' to 'Edit {Title}'
- Use template part entity title (e.g., 'Edit Header', 'Edit Footer')
- Fall back to 'Edit template part' if no title is available
- Maintain existing functionality for Navigation editing

- Wrap each button in ToolbarGroup components for proper visual separation
- Use standard WordPress UI components (ToolbarGroup) instead of custom CSS
- Maintain existing functionality while improving visual organization
- Follow WordPress design system best practices

- Replace ToolbarGroup approach with different BlockControls group props
- Use group='block' for Template Part Edit button and group='other' for Navigation Edit button
- WordPress automatically adds visual separators between different groups
- Add documentation comment explaining the prototype hack approach
- Maintain existing functionality while improving visual organization

- Convert template part titles to lowercase for consistent sentence case
- Button now shows 'Edit header' instead of 'Edit Header'
- Maintains fallback to 'Edit template part' when no title is available
- Improves visual consistency with other button labels