[kibanaUtils] Reduce page load bundle to under 100kB

[tylersmalley]

For details, refer to the meta issue at #95853

The kibanaUtils plugin is currently 146,560 bytes. To consider this issue closed, the limits.yml should be updated with the value under 100000.

[elasticmachine]

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

[streamich]

This needs discussion on how to approach it. App Services team is the main maintainer of the kibana_utils plugin, but not all code there is directly maintained by us. It is like a kitchen sink for utility code.

Possible solutions would be:

• We create "utils" plugins for each team separately, in their domain, e.g. kibana_app/utils.
• Or we allow deep imports from kibana_util plugin, so that other teams can only import what they need (but that would not work with our current .js bundling way, where each plugin is its own whole bundle).

[tylersmalley]

@streamich, I think a package would be a much more appropriate place for utilities and would delegate bundle size to the consumer. A plugin that is just a dumping ground for shared utilities is the issue. We shouldn't be loading all these utilities on every page load.

[Dosant]

KibanaUtils are under 100Kb, closing this one 🎉 and opened an issue for further improvements: #114988