[Kubernetes Otel] Update Events Visualisations for EDOT

[gizas]

We will need to update the Events Visualisation filters for our Kubernetes Otel content package once the following upstream issue is merged and becomes available in EDOT Collector.

The upstream issue will affect the datastream that our events will be sent, so we anticipate that our Visualisations will need an update.

Goals

• Check that the K8s Otel Dashboard shows the Warning/Errors
• Check the final mappings of related event fields like body.structured.object.kind are searchable
• Check that updating the time range in Visualisations does not break the user experience

[ChrsMark]

@gizas open-telemetry/opentelemetry-collector-contrib#42290 is now available in EDOT Collector after https://github.com/elastic/elastic-agent/pull/9858/files#diff-a949f452735573d27a9d587c585e806e2b7a6956aa47c09b169a687e2e8fbef4R46 got merged. This change will be shipped with of the 9.2 release of EDOT Collector. Should the Integration be changed accordingly?

[ChrsMark]

@gizas @mlunadia even if we change the data_stream.dataset filters to be based on k8sobjectsreceiver.otel, we still face the body.structured.* fields being non-searchable. What do you think about switching to using the data coming from the k8seventsreceiver.otel dataset since [otel] Introduce k8sevents otel receiver as downstream component elastic-agent#9791 will be available for 9.2 anyway?

[gizas]

Agree on waiting until 9.2!