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).

Currently route definitions exists as a single file, like apm/server/routes/errors.ts. And the logic for the route exists in
https://github.com/elastic/kibana/tree/e771748d96ba098e2e35cf98a010f4f2a23c9c39/x-pack/plugins/apm/server/lib/errors.

I propose that the route

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

{
+  "type": "commonjs",
}