[data views] Review data views plugin / strategy for reducing bundle size

[mattkime]

Follow up to #113497

We need to review our strategy for reducing the data plugin bundle size. The data view code was broken out into its own plugin which resulted in a 11k increase in total bundle size. The core team may have suggestions for better strategies.

part of #84788

[mattkime]

@spalger Should you be involved in this or someone else on your team? Should we do this async or sync? How much time should we dedicate to coming up with a strategy for data views? More or less than 2 hours?

[Dosant]

The actual issue: #84788

just leaving a note, that we plan to address all the "Aggs" part of a bundle with using async registry pattern that we started working at: #65993

[spalger]

I'd be happy to be part of the process. I think we could talk about strategy in this issue, but I generally find it's a lot more efficient to do on a call. I wouldn't expect such a call to take more than 2 hours.

[elasticmachine]

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

[kertal]

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.