[otel] Introduce k8sevents otel receiver as downstream component

[ChrsMark]

Describe the enhancement:

The k8seventsreceiver is not going to get deprecated eventually: open-telemetry/opentelemetry-collector-contrib#24242

Hence this component can be used directly for collecting K8s Events without the need for additional transform actions.

Describe a specific use case for the enhancement or feature:

As described at elastic/integrations#15127 the usage of the k8sobjects receiver for K8s Events collection comes with several limitations. Using the specific k8sevents receiver directly will help improving the out of the box experience.

What is the definition of done?

1. Include the k8sevents receiver as an EDOT Collector component: Add k8seventsreceiver otel component #9826
2. Enhance the kube-stack values file to make use of it (it can be shipped in the same PR with the above): [kube-stack] Add k8s events receiver #10086
3. Mark k8sobjects receiver for removal from the kube-stack configurations: [kube-stack] Add k8s events receiver #10086
4. Test (only) the K8s OTel content pack and verify that K8s Events panels can be tuned to work with data coming from the k8sevents receiver. The integration will be updated in follow-up PR in later release: [kube-stack] Add k8s events receiver #10086

[gizas]

Thanks Christos. This feels the correct direction to me. Lets not forget to also document any changes that this new introduction will bring. Especially I am anticipating the dedicated datastream name for the events that we need to specifically document for our users

[ChrsMark]

Closing this one, as the component is now available in EDOT and enabled in kube-stack.
elastic/integrations#15454 will update the dashboards accordingly.