[Discover][Obs ai assistant] Set the index pattern on the context api to generate correct ES|QL queries etc

[stratoula]

Summary

Sets the index pattern correctly in the obs ai assistant.
The Obs ai assistant is part of Discover in serverless Oblt project and can also be set up everywhere from the Observability AI Assistant scope advanced setting. It is a very useful tool for the Discover users and for moving from KQL to ES|QL world.

This is important for prompts such as:

• Transform the KQL and filters to ES|QL

• More

Other interesting prompts:

• Equivalent of KQL of where filters

• Explain the ES|QL query

• Run questions on your dataset and unified search bar selection

[stratoula]

/ci

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 3ff3d51

Metrics [docs]

Async chunks

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

id	before	after	diff
discover	635.6KB	635.9KB	+287.0B

Page load bundle

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

id	before	after	diff
discover	34.8KB	34.9KB	+52.0B

History

• 💚 Build #206323 succeeded 86b3162
• 💔 Build #205858 failed bbd7e85
• 💔 Build #204853 failed aac96a0
• 💔 Build #204326 failed 75f5d4e
• 💔 Build #204315 failed 56f560d

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[jughosta]

Should be probably aligned with

• [Discover][Observability] Register Observability AI Assistant feature #181976

[stratoula]

Maybe it is not clear from my description but this is a bug fix, the index pattern is not correctly passed to the LLM creating wrong ES|QL queries. This functionality is already out in the wild, I am not adding something new here (from the functionality perspective), I am fixing a bug.

[dgieselaar]

LGTM (on the AI Assistant usage)

[stratoula]

Gathering here the outcome of an offline discussion I had with some folks:

• the Obs ai assistant is built as a platform tool and has very few dependencies so we can use it in Discover plugin and we dont need a middleware

"actions",
"features",
"licensing",
"security",
"taskManager",
"dataViews"

• there is no advantage of adding a middleware (also we are adding xpack plugins dependencies all the time)
• this PR is fixing an existing but which will also benefit the Logs Discover
• in the future we might need a middleware (for example when the security ai assistant also provides the same capabilities). At this point this is not possible, we can always adapt later.

[jughosta]

Code changes LGTM

[delanni]

Reverted in #182088