[DOCS-15447] Use DO version of Metabase README

[evazorro]

Companion to documentation#39739, which reduces the duplicate Data Observability copy of the Metabase docs to a stub. This PR moves the content that only existed in that copy into the README.

Follows the same pattern as the Hex pair (internal-core#3918 / documentation#39211).

• Added a What's next section with the sync latency note and a link to the Data Observability Catalog
• Added framing to clarify that lineage requires a data warehouse connected to Datadog. Scoped to lineage, since log collection has no such requirement
• Fixed the account configuration table against the actual tile: added the missing Account name row, and dropped the "Metabase" prefix from the other labels so they match the form. This also cleared two Vale warnings (via and e.g.,)

Remaining Vale warnings in this file are all on pre-existing lines I didn't touch ("Log into" and the SAML/SSO note).

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: 0 selected, 0 skipped (of 0 test tasks)
Publish tasks:   2 (always emitted)
Diff (1 file):
  metabase/README.md

Debug a specific task: evalya plan impact --path <path> --task <task>

Learn more about CI impact filtering

[dd-octo-sts]

Validation Report

Validation	Description	Status
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	❌

Run ddev validate all changed --fix to attempt to auto-fix supported validations.

Passed validations (20)

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run

[datadog-datadog-prod-us1-2]

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 1 Pipeline job failed

Validate repository | Run Validations / Validate

View more details · View in GitHub Actions

PR #25123 is missing an Agent-release QA decision label. Every pull request must declare whether its changes require QA validation.

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 5318c39 | Docs | View more details | Give us feedback!}