Navigation conversion scenarios need comprehensive entity binding coverage

What

Navigation conversion processes need comprehensive coverage to ensure entity bindings are properly created for dynamic URL resolution across all conversion scenarios.

Why

Currently, there are multiple conversion paths that create Navigation Link blocks but don't include the required entity bindings for dynamic URL resolution. This causes converted links to lose their connection to underlying page entities, breaking the dynamic URL functionality introduced in #71630.

Conversion Scenarios That Need Coverage

1. Page List to Navigation Link conversion

• Status: Fixed in PR #72287
• Issue: Page List blocks converted to Navigation Links were missing entity bindings
• Impact: Links lose dynamic URL resolution when page URLs change

2. Classic Menu to Navigation Link conversion

• Status: Fixed in PR #72289
• Issue: Classic Menu items converted to Navigation Links were missing entity bindings
• Impact: Links lose dynamic URL resolution when page URLs change

How

1. Audit all conversion paths that create Navigation Link blocks
2. Ensure entity bindings are included in all conversion scenarios
3. Create shared utilities for consistent entity binding creation
4. Add comprehensive test coverage for all conversion scenarios
5. Document conversion requirements for third-party developers

Start by auditing conversion paths that create Navigation Link blocks, using the entity-binding behavior introduced in #71630 and the fixes in #72287 and #72289 as references. The work is done when all conversion scenarios preserve entity bindings, have comprehensive tests, and the conversion requirements are documented for third-party developers.