elasticsearch

For the JarHell Bootstrap Check, a user is seeing the following:

java.lang.IllegalStateException: failed to load plugin x-pack-core due to jar hell
at org.elasticsearch.plugins.PluginsService.checkBundleJarHell(PluginsService.java:524) ~[elasticsearch-7.6.2.jar:7.6.2]
at org.elasticsearch.plugins.PluginsService.loadBundl

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

Above the fields list and in the layer pane, change Change index pattern to Index pattern.

Above fields list:

In layer pane:
![Screen Shot 2021-07-15 at 3 23 11 PM](https://user-images.githubusercontent.com/38990715/125852638-d794c03c-86b1-4

As suggested in the ESM guidelines of Node.js it would be good to explicit the type of the module.

{
+  "type": "commonjs",
}