[GS] add the provider field to GlobalSearchResult

[pgayvallet]

Summary

Related to #68619

Add a provider field to the result type to allow consumers to access this information. Main use case would be for sorting results by provider.

Checklist

• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 3fb8b62

History

• 💔 Build #53270 failed 257692e

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

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[joshdover]

This does make the the Global Search API a slightly leaky abstraction...consumers now will need to have up-front knowledge of the registered providers in order to display them in the preferred order.

This is probably the most practical option though. The only other option I see is having providers register an order parameter that is used to rank results, similar to how applications specify their order in the Chrome nav. However, I think that just makes consuming this API less flexible.

[pgayvallet]

This does make the the Global Search API a slightly leaky abstraction...consumers now will need to have up-front knowledge of the registered providers in order to display them in the preferred order.

I agree, we are leaking something that maybe should remain an implementation detail of the API.

Also, specifically for the searchbar needs for v1, it should be possible to sort by type, or at least to put the application type results on top, and the other kind sorted by score afterward.

I was more doing this as preliminary work for the next step, when we'll have multiple providers returning the same kind of results (I'm thinking SO results from other spaces for instance)

Maybe the meta field could be used instead, by storing the associated space for example, and this PR is unneeded.

I'm going to close it for now, as it should not be needed in the short term. We'll see if we'll need to reopen it later.