[databricks] Dashboard: group by workspace_name + add template variable

[charlesmyu]

What does this PR do?

Updates databricks/assets/dashboards/databricks_cost_overview.json:

• Switches the two "Cost by Workspace" graphs (scalar + timeseries) from by {workspace_id} to by {workspace_name}, so the grouped buckets surface the human-readable workspace name rather than the numeric Databricks workspace ID.
• Adds a new workspace_name template variable alongside the existing workspace_id, with prefix: "workspace_name" and default: "*", following the pattern of the other template vars on this dashboard.
• Applies $workspace_name to every query on the dashboard alongside the existing $workspace_id, so the new template variable narrows all panels consistently.

Do not merge until https://github.com/DataDog/dogweb/pull/167610 is merged and deployed, which actually pulls in the "workspace_name" tag

Motivation

The Databricks CCM crawler now emits a workspace_name tag on every line item (DataDog/dogweb#167610), which is the human-readable workspace label rather than the opaque numeric workspace_id. The cost-overview dashboard should take advantage of that tag:

• "Cost by Workspace" buckets become readable at a glance (e.g. "prod-analytics" instead of 8237401234567890).
• Users can filter the dashboard by workspace using the friendly name.

Both tags continue to be available — this is purely additive on the filter side; the only group-by change is on the two panels explicitly titled "Cost by Workspace".

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• 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

🤖 Generated with Claude Code

[datadog-datadog-prod-us1-2]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

Validate repository | Run Validations / Validate     

🛟 This job is unlikely to succeed on retry. Please review your pipeline configuration.

Missing Agent-release QA decision label for PR #23854. It must be labeled as 'qa/required' or 'qa/skip-qa'.

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: d347b7a | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and Codecov 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	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
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