[Kubernetes Opentelemetry Assets]: Pod drilldown on k8s.object.name

### Integration Name

Kubernetes OpenTelemetry Assets [packages/kubernetes_otel]

### Dataset Name

_No response_

### Integration Version

2.4.1

### Agent Version

9.4.5

### Agent Output Type

elasticsearch

### Elasticsearch Version

9.4.5

### OS Version and Architecture

Ubuntu

### Software/API Version

_No response_

### Error Message

_No response_

### Event Original

_No response_

### What did you do?

1 - Deploy EDOT via opentelemetry-kube-stack Helm chart 0.20.4
2 - Install kubernetes_otel v.2.4.1 assets in Kibana
3 - Open the dashboard [Kubernetes OTel] Pod Detail, click on "View pod logs in Discover"

### What did you see?

Discover open with "k8s.object.name" and shows no results

### What did you expect to see?

While the same query on "k8s.pod.name" returns the expected documents.

### Anything else?

The change that introduced the behavior is https://github.com/elastic/integrations/pull/20410

Note that k8s.object.name is not part of the Otel sementic (https://opentelemetry.io/docs/specs/semconv/resource/k8s/#pod)
The only reference I found is in the k8seventsreceiver : https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/k8seventsreceiver/README.md

So this attribute only exists on Kubernetes events, while container logs, traces and metrics all follow the standard k8s.pod.name

Start in packages/kubernetes_otel and inspect the change from pull request 20410, focusing on the [Kubernetes OTel] Pod Detail dashboard's "View pod logs in Discover" action. Verify the current query against k8s.object.name, update it to match the documented pod field, and confirm Discover returns the expected documents like a k8s.pod.name query.

Written by the indexing model from the issue text.