[ES|QL] Editor extensions registry - recommended queries

[stratoula]

Summary

Closes #200026

Scope

This PR is allowing the solutions teams to register extensions to the editor. The first extension is the recommended queries. I prefer to add extra extensions in follow up PRs mostly to keep it clean and also because I want to see the usage first.

These extensions should not appear in the classic mode. They should appear only on the solution that they are being registered for.

Some examples below:

• Only static suggestions, for index without solution extensions

• Additional suggestions, for index with solution extensions

Some more technical notes

• I am creating a server side registry in the esql plugin. I considered to create a plugin from scratch but I decided against it as at this point is only esql related extensions and we are trying to keep our plugins number as low as possible. It can get moved to another plugin if we ever decide in favor of it.
• Each solution can register in their plugins their extensions. I have added a Readme which I hope it helps but this is how it should look

const esqlExtensionsRegistry = esql.getExtensionsRegistry();
        esqlExtensionsRegistry.setRecommendedQueries(
          [
            {
              name: 'Logs count by log level',
              query: 'from logs* | STATS count(*) by log_level',
            },
            {
              name: 'Apache logs counts',
              query: 'from logs-apache_error | STATS count(*)',
            },
            {
              name: 'Another index, not logs',
              query: 'from movies | STATS count(*)',
            },
          ],
            'oblt'
        );

• I preferred a server side registry for multiple reasons:
  • In the case we want to make it more advanced in the future (more checks, LLMs etc) it make more sense to have a server side solution
  • It is more performant to do some checks such as (does this source exist?) etc
  • It allows me to create a route to get these extensions. I am using this route to get the extensions to the editor but in the future we could use the same route to display these extensions in a flyout or wherever the solutions teams want

Note

This PR is not registering anything at the editor but just sets up the architecture. The registration of recommended queries should happen from the solutions teams in their plugins.

Checklist

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

[stratoula]

I need to test with the code scanner

[stratoula]

Update: Tested! Code scanner passes ✅

[sddonne]

Looks amazing!

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 94f48a4

Failed CI Steps

• FTR Configs #13
• FTR Configs #68

Test Failures

• [job] [logs] FTR Configs #68 / Rules Management - Rule Import & Export APIs @ess @serverless @serverlessQA import_rules importing rules with an index should set the response content types to be expected

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
esql	230	232	+2
stackAlerts	284	286	+2
total			+4

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/esql-types	31	39	+8
@kbn/esql-validation-autocomplete	164	166	+2
@kbn/monaco	183	185	+2
esql	11	13	+2
total			+14

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
esql	247.4KB	247.9KB	+550.0B

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
esql	1	2	+1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
esql	8.1KB	8.7KB	+613.0B
kbnUiSharedDeps-srcJs	3.7MB	3.7MB	+651.0B
total			+1.2KB

Unknown metric groups

API count

id	before	after	diff
@kbn/esql-types	32	40	+8
@kbn/esql-validation-autocomplete	185	187	+2
@kbn/monaco	183	185	+2
esql	32	34	+2
total			+14

History

• 💛 Build #304067 was flaky 58473d4
• 💔 Build #303659 failed 3f70510
• 💔 Build #303637 failed 3d50a76

[kibanamachine]

Starting backport for target branches: 8.19

https://github.com/elastic/kibana/actions/runs/15436729493

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation