update metabase tile overview to include lineage crawler info

[himakolavennu]

What does this PR do?

Updates Metabase tile description to describe data lineage functionality

Motivation

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[github-actions]

⚠️ Recommendation: Add qa/skip-qa label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[rtrieu]

minor suggestion, but otherwise looks good!

Review from BoyangHuang is dismissed. Related teams and files:

• saas-integrations
  • metabase/README.md

[himakolavennu]

/merge

[dd-devflow-routing-codex]

View all feedbacks in Devflow UI.

2026-01-06 20:23:38 UTC ℹ️ Start processing command /merge

---

2026-01-06 20:23:43 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-01-07 00:24:11 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

[himakolavennu]

/merge

[dd-devflow-routing-codex]

View all feedbacks in Devflow UI.

2026-01-07 15:24:28 UTC ℹ️ Start processing command /merge

---

2026-01-07 15:24:41 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-01-07 15:44:47 UTC ℹ️ MergeQueue: This merge request was already merged

This pull request was merged directly.