[data.search] Make execution context required

[lukasolson]

Related to #101587.

Currently, when calling data.search, it accepts an options parameter that currently includes a number of things as well as the following:

export interface ISearchOptions {
  // ...
  executionContext?: KibanaExecutionContext;
}

We would like to make executionContext a required parameter so that queries can be traced back to their origins. Since both expressions (esaggs and esdsl) and search source call data.search internally, we need to update these interfaces to also require execution context.

The following usages need to be updated to pass in execution context:

• Search source (which calls data.search internally)
  • Search examples app
  • Terms agg post flight request
  • Maps app
  • Security Solution Fleet Osquery
• EQL search
• ES search (_search)
• ES search (_async_search)
• Data visualizer
• Infra data search
• Timeline search

This is a just a preliminary search, there may be other places we need to add this.

/cc @mshustov

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

[lizozom]

Following the merge of #124996, most of the context is specified on the top most level by using the core ExecutionContextService. The request specific context is used only for overrides where necessary, so I don't believe it should be mandatory.

I believe this issue can be closed.