[ES|QL] Prioritize fields based on ecs information on the editor

[stratoula]

Describe the feature:

Right now, we are suggesting fields based on the alphabetical order. In case of ECS we want to suggest first the fields that are defined in the schema.

I think the logic of retrieving this ECS schema logic should live outside the editor, possibly on a package.

[elasticmachine]

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

[drewdaemon]

I think the logic of retrieving this ECS schema logic should live outside the editor, possibly on a package.

@kertal this need dovetails nicely with your ECS field-descriptions PoC

[drewdaemon]

Right now, ECS info is available as an in-memory browser bundle. However, the @elastic/kibana-data-discovery team has discussed making a server-side API for retrieving ECS data in more efficient, specific way.

[stratoula]

yes I would love to use this here

[kertal]

Yes, this is something we should discuss, so what I did was doing a POC for a browser side solution (problem: async bundle size additions, and a push back on making it a shared dependency)
#180230
And a follow up to figure out, what happens when moving it to server side, no bundle size issues (but also not mergable)
#180543

[kertal]

FYI, another intiative related to this topic: https://github.com/elastic/observability-dev/issues/3331