Entity definition use case

Currently the Elastic Entity Model has hard-coded entity definitions ([https://github.com/elastic/kibana/blob/main/x-pack/plugins/observability_solution/entity_manager/docs/entity_definitions.md](https://www.google.com/url?q=https://github.com/elastic/kibana/blob/main/x-pack/plugins/observability_solution/entity_manager/docs/entity_definitions.md&sa=D&source=docs&ust=1723159504826016&usg=AOvVaw2pOMJ-VKwNhjN-aBCtkkuN))

We would like to have packages include entity definitions (for instance, a kubernetes package could contain entity definitions for k8s.pod, k8s.node, etc.)

While everything related to entities currently happens in Kibana/ES, it would also be possible to do entity discovery in the otel collector, in which case we would want to distribute the entity definition assets to the collectors.