* mysql: pass timerange for template variable queries

* mysql: document time range macro usage in template variables

* mysql: docs for on time range change refresh mode for template queries

* Revert "mysql: docs for on time range change refresh mode for template queries"

This reverts commit 5325972aa4f66257aa20f7ae6d4de8fa8fe628b6.

* pass timerange for template queries when refresh is set to timerange
change

* document on time range change refresh mode for template queries

named metric is present

This commit makes it possible to set min interval per panel.
Overrides the value configured on the datasource.

ref #9705

* added tooltip, fixes #10092

* fixed code formatting

the dsType property caused some confusion about what datasource is
beeing used. I just removed it since it not beeing used.

closes #10072

add Cloud Alchemy Ansible role

fix render http[get] params error

closes #10046

Use systemd notification where applicable

With this change in place, the grafana service will signal
readiness to serve by writing "READY=1" to the path specified
through the NOTIFY_SOCKET environment variable. If this
environment variable is not present or empty, no notification
will happen. This notification is the standard systemd
mechanism for indicating a service is ready to serve. For
Grafana this may be a couple of seconds from startup due to
database migrations. This change also adjusts the Grafana
systemd service definition to make use of this feature.

grafana-10039: fix query time range ends in the past

Revert "prometheus nested query support"