Dashboards: `${__to:date:M}` and related time variables are evaluated in local browser time even when dashboard timezone is set to UTC

### What happened? **🐛 Bug Report** When using `${__to:date:M}` (or similar date formatting on `__from` / `__to`), the value is evaluated based on the client’s local time zone, even when the dashboard is explicitly set to UTC. This leads to inconsistencies for users in different time zones, especially in Prometheus queries where the month is compared against the result of `month()` (which always uses UTC). This breaks query logic across time zones and results in incorrect panel rendering. **🔁 Steps to Reproduce** 1. Create a dashboard with timezone set to "UTC". 2. Add a panel with the following query (Prometheus example): `month() == bool vector(${__to:date:M})` 3. View the panel from a browser in: * New York (UTC-4) * Stockholm or Berlin (UTC+2) 4. Observe that the query behaves differently in each timezone — e.g., users in Europe may see a flat line, while US users see the correct monthly burn curve. **🧠 Expected Behavior** When a dashboard is set to UTC, all built-in time variables (like` __from`,` __to`, and their `:date:` formats) should be evaluated in UTC, not in the client’s local timezone. **📎 Use Case** Prometheus users often compare the current month in UTC using queries like: `month() == bool vector(${__to:date:M})` When `${__to:date:M}` is evaluated in local time and `month()` is evaluated in UTC, this comparison breaks — making panels unreliable for users outside UTC-0. **✅ Suggested Fix** Modify the rendering logic for `${__from}` / `${__to}` and their `:date:...` formats so that: * If the dashboard timezone is set to UTC, `__from` and `__to` are formatted in UTC. * Otherwise, fallback to client local time (current behavior). This will ensure consistent behavior across users and dashboards, especially in multi-timezone teams. **📦 Affected Versions** Observed in: * Grafana v11.6.1 (ae23ead4d9) * Grafana v12.0.0 (4c0e7045f9) Likely affects: all recent versions where `${__to}` date formatting is client-side **🙏 Additional Context** Two related PR…