[Lens] do not fail on conflict fields

[stratoula]

From Security solutions:

I have a field, source.ip which has conflict type text and keyword, it shows error in Lens when doing aggregation, but in Dev tools and all the Elasticsearch api does not show error in this case. Would like to know if there’s a chance we could align the rendering logic of Lens with the search result?
Asking because Security Solution is migrating charts rendering with Elastic charts to Lens Embeddables. The current charts fetches data with Elasticsearch api, therefore shows no error when aggregating on a conflict field, but Lens Embeddables shows error on the conflict field. We’d like to fix this inconsistency as conflict fields are actually quite common from users, it might be a bit frustrating if we show error when aggregating on conflict fields.

Originally posted by @angorayc in #143673 (comment)

[elasticmachine]

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

[markov00]

In order to provide better transparency of priorities, issues that will not be prioritized within the next 24 months are being closed.

Tracking request in Lens general improvements ice box #184459