Add comprehensive DB-UI to DB-UX-DSv3 component migration guide

[Copilot]

This PR addresses the request for a comprehensive migration table that maps DB-UI components without direct equivalents in DB-UX Design System v3, providing clear guidance on how to handle each component.

What's Added

New Migration Document: docs/migration/db-ui-to-db-ux-dsv3.md

This comprehensive guide includes:

• Complete component mapping table with status indicators for all mentioned DB-UI components:

  • 🔁 Available replacement - Use suggested alternative component(s)
  • 🔄 Planned for future - Component in roadmap, use temporary solution
  • ❌ Not planned - Use alternative approach or build custom solution

• Specific migration strategies with code examples for:

  • Layout components (rea-main, rea-grid, rea-footer)
  • Interactive elements (elm-headline, elm-loadingindicator, elm-progress, elm-chip)
  • Navigation components (cmp-breadcrumb, cmp-pagination, cmp-table, cmp-sidenavi, cmp-dialog)

• Practical guidance including:

  • Migration code examples showing before/after
  • Accessibility considerations for custom implementations
  • Timeline for planned components (Q2/Q3 2024)
  • Links to relevant research documents and existing components

Enhanced Discoverability

• Added reference to the new guide in docs/migration/v0.7.x-to-v1.0.0.md
• Added link in main README.md migration section for better visibility

Example Migration Guidance

For elm-chip → db-tag:

<!-- DB-UI -->
<div class="elm-chip" data-variant="primary">
  Chip Text
</div>

<!-- DB-UX-DSv3 -->
<db-tag>
  <db-button variant="ghost">Chip Text</db-button>
</db-tag>

For cmp-sidenavi → db-navigation + db-drawer:

<db-drawer>
  <db-navigation>
    <db-navigation-item>
      <db-link href="/page1">Navigation Item 1</db-link>
    </db-navigation-item>
  </db-navigation>
</db-drawer>

The guide provides exactly what was requested - a clear table showing how to handle each DB-UI component without direct DB-UX-DSv3 equivalents, with actionable statements like "use instead x in combination with y", "coming in Qn/202X", or "build it yourself" as specified in the issue.

Fixes #4864.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8631f3b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[gnuheidix]

You've done a great job so far. :-)

I think you mean the year 2025 or 2026 instead of 2024, am I right?