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"

prometheus nested query support

Should use case insensitive matching when searching for users

Use docker tmpfs mounts for mysql and postgres data volumes

Fixes #10012

export view json now templatized, fixes #10001

migrated four files from js to ts

* migrated gfunc from js to ts

* deleted gfunc.js, small fixes in gfunc.ts

* migration of org files from js to ts

* more migration of org files to ts

* minor fix to change_password

* renamed files

* four files js to ts, fixed ng_model_on_blur

* added /** @ngInject */

Optimized number of lines fetching in log file initialisation

Added unit tests for file logging line counting

Remove file after unit test

Elasticsearch max_concurrent_shard_requests parameter for es 5.6+

* converted files from .js to .ts

[GCS] Support for gcs path

closes #9955

Fixes #9649