UI: Use link styling for Dag tags

[parkhojeong]

Why

Dag tag links are currently rendered as plain text, making their clickable behavior less obvious

Fix

Using Chakra Link with styling helps users more easily recognize each tag as clickable.
Application scope: Dags list and Dag details header

• Light mode

Screen.Recording.2026-05-12.at.21.07.42.mp4

• Dark mode

Screen.Recording.2026-05-12.at.21.12.06.mp4

---

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

• Yes (please specify the tool below)

[choo121600]

I agree that the tags currently don’t read as clearly clickable.

One suggestion: rather than using an inline-style-based custom background approach that partially bypasses the Chakra styling system, would it make sense to reuse the existing text-link pattern already used in DagsList.tsx for the DagId links?
(Since tags are secondary metadata, we could omit fontWeight="bold".)

<Link asChild color="fg.info">
  <RouterLink to={...}>{...}</RouterLink>
</Link>

[parkhojeong]

@choo121600

Thanks for the suggestion. It makes sense. Addressed in 46faf67
The PR title and description were also updated

Screen.Recording.2026-05-12.at.21.07.42.mp4

[parkhojeong]

The failing CI job appears unrelated to this PR. It failed while logging in to ghcr.io during the CI image build

[bbovenzi]

In a follow up PR, we should just make a custom RouterLink component to remove all the repeated

<Link asChild color="fg.info"><RouterLink /></Link> code

[parkhojeong]

In a follow up PR, we should just make a custom RouterLink component to remove all the repeated

<Link asChild color="fg.info"><RouterLink /></Link> code

Good idea. I'll open a follow-up PR for that.

[github-actions]

Backport successfully created: v3-2-test

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