UI: Add custom RouterLink component

[parkhojeong]

Follow-up to #66750 (comment)

the repeated code is in multiple places: <Link asChild color="fg.info"> <RouterLink /> </Link>
This PR introduces the custom RouterLink component and applies it to a small initial set of usages.

• Once the component API is agreed on, I can migrate the remaining repeated usages.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

[bbovenzi]

Looks great! Let's apply it everywhere

[choo121600]

Cool :)

[choo121600]

@parkhojeong — Your unresolved review thread(s) from @bbovenzi appear to have been addressed (post-review commits and/or in-thread replies on every thread, with the latest commit pushed after the most recent thread). I've added the ready for maintainer review label so the PR re-enters the maintainer review queue.

@bbovenzi — could you take another look when you have a chance? If you agree the feedback was addressed, please mark the threads as resolved so the queue signal stays accurate. If a thread still needs work, please reply in-line — @parkhojeong will follow up.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

---

Drafted-by: Claude Code (Opus 4.7); reviewed by @choo121600 before posting

[choo121600]

Looks like the CI failure is unrelated to this PR. I'll rerun it :)

[github-actions]

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.2.3 based on: backport label targeting v3-2-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 42a85ee v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[choo121600]

Automatic backporting failed due to conflicts in 4 files, including DeadlineRow.tsx.
Since this is a refactor (not a bug fix), I’m removing the backport label for now.