Navigation conversion scenarios need comprehensive entity binding coverage

[getdave]

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 Fix Page List to Navigation Link conversion with entity bindings #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 Fix Classic Menu to Navigation Link conversion with entity bindings #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

[t-hamano]

This issue was discussed at today's bug scrub.

This issue looks like a tracking issue, is that correct? Just in case, I'll move it to the Iteration/Tracking Issues column.

[getdave]

I think ideally we'd get the coverage in but it's not a blocker for 6.9

[t-hamano]

Since the RC1 release is about to begin, I'm punting this issue to Punted to 6.9.1. If Punted to 7.0 is more appropriate, feel free to move the milestone.