[Unified search] Display the solutions recommended queries in the help menu

[stratoula]

Summary

Reopening of #223362

In #221474 we introduced the mechanism to register queries per solution at the editor.

This PR displays these queries in the unified search menu too. In the following screenshot the 2 first queries are the oblt solution registered queries. I also have a max-height just to be sure that this list doesnt get too long now that the solutions can register queries.

Note

This change won't display anything in the popover as no solution has registered any queries yet. This PR sets the mechanism though on when they will do so.

How to test

If you want to test it the fastest way is to go to the esql plugin (server side) and add (change the examples as you wish):

this.extensionsRegistry.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'
    );

Then go to Discover (solutions mode) and type from logs* and hit the query. Open the popover and check the 2 first recommendations are been suggested.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/kibana-esql (Team:ESQL)

[stratoula]

I merged it by mistake and reverted it, so I open it again. ES|QL team had approved and was missing the team presentation review. @nreese had started it already here #223362 and I had addressed all his comments. Let me know if there is anyting else.

I am so sorry for the inconvenience. I did it by mistake.

[nreese]

kibana-presentation changes LGTM
code review only.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 6758257

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
cloudSecurityPosture	704	705	+1
controls	355	356	+1
dashboard	669	670	+1
data	534	535	+1
datasetQuality	439	440	+1
dataVisualizer	760	761	+1
discover	1307	1308	+1
esql	236	237	+1
esqlDataGrid	437	438	+1
eventAnnotationListing	592	593	+1
infra	1468	1469	+1
lens	1437	1438	+1
lists	461	462	+1
maps	1282	1283	+1
ml	2406	2407	+1
observability	1304	1305	+1
observabilityAIAssistantApp	318	319	+1
securitySolution	7600	7601	+1
slo	1178	1179	+1
stackAlerts	290	291	+1
streamsApp	505	506	+1
triggersActionsUi	874	875	+1
unifiedSearch	395	396	+1
total			+23

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	44	45	+1
unifiedSearch	113	114	+1
total			+2

Async chunks

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

id	before	after	diff
esql	256.3KB	255.6KB	-677.0B
unifiedSearch	360.9KB	361.8KB	+940.0B
total			+263.0B

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.8KB	9.2KB	+382.0B

Unknown metric groups

API count

id	before	after	diff
@kbn/esql-types	45	46	+1
@kbn/esql-validation-autocomplete	189	191	+2
unifiedSearch	151	152	+1
total			+4

History

• 💔 Build #307990 failed eb368ce

[kibanamachine]

Starting backport for target branches: 8.19

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

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 223602

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 223602 locally
cc: @stratoula

[stratoula]

💚 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