Grafana Dashboard Incorrect Timezone Handling for Non-UTC Databases

### What happened? I have encountered a bug in the Grafana dashboard regarding timezone conversion. It appears that Grafana only supports conversion for UTC timezones. Steps to Reproduce: Set up a database (DB) with a timezone of UTC+2. Ensure the database is configured correctly, displaying data with the UTC+2 offset. Insert a record with the original UTC timestamp: 2024-04-26 10:05:34.000 (UTC). In the database, the value should be stored as 2024-04-26 12:05:34.000 (UTC+2). Expected Behavior: When viewing this data in the Grafana dashboard, the displayed time should match the database value of 2024-04-26 12:05:34.000. Actual Behavior: However, Grafana is displaying the time as 2024-04-26 14:05:34.000, which indicates that it is incorrectly converting the time, possibly treating it as UTC without accounting for the database's configured timezone. Additional Information: This issue may affect users who are working with databases in non-UTC timezones, leading to confusion and potential errors in interpreting time-related data. Thank you for addressing this issue! ### What did you expect to happen? Expected Behavior: When viewing this data in the Grafana dashboard, the displayed time should match the database value of 2024-04-26 12:05:34.000. Actual Behavior: However, Grafana is displaying the time as 2024-04-26 14:05:34.000, which indicates that it is incorrectly converting the time, possibly treating it as UTC without accounting for the database's configured timezone. ### Did this work before? no ### How do we reproduce it? set TZ=UTC+2 ### Is the bug inside a dashboard panel? _No response_ ### Environment (with versions)? Grafana: OS: Browser: ### Grafana platform? Docker ### Datasource(s)? 11.0.0