Add and use pod labels to avoid having to query all pods from kubernetes

[otrosien]

One-line summary

Implements pod labeling optimization for Kubernetes Elasticsearch operator to avoid querying all pods.

Issues

• Fixes Add and use pod labels to avoid having to query all pods from kubernetes #461

Key Changes:

• Added migration logic in setupInformers() to ensure all existing EDS pods have the es-operator-dataset label
• Modified collectResources() to use label selectors when fetching pods for each EDS
• Updated templateInjectLabels() to always set labels (removed conditional check)
• Added comprehensive logging and annotation-based migration tracking
• Created E2E test to verify pod label migration functionality
• Introduced new annotation es-operator.zalando.org/pod-label-migration-complete to track migration status

Impact:

• Core change to pod discovery mechanism that could affect all EDS resources
• Migration runs on every operator startup (with annotation-based skip logic)
• Performance improvement expected from targeted pod queries vs. listing all pods

Types of Changes

• New feature (non-breaking change which adds functionality)

Review

List of tasks the reviewer must do to review the PR

• Tests
• Documentation
• CHANGELOG

Deployment Notes

• Document migration steps

[zalando-compr-opensource]

invalid team ID

The team ID in your .zappr.yaml file does not appear to be valid. Please, fix
this before team ID checks will be added back into ComPR's specification check.

You can follow this guideline for help.

[zalando-robot]

Deployment Checklist

This change falls under the deployment policy.

💁 Since Nov 10th, we are in the RED deployment zone. This means all changes released to production must adhere to the following requirements:

• Detailed release notes are provided in this PR’s description.
• Thorough load-testing has been performed, and is documented in the description/comment.
• You can enable/disable the change via feature toggles, and have confirmed these toggles work as expected.
• Technical review: A Principal Engineer, Engineering Manager or Head of Engineering have green-lit your changes, and the reviewer is named in the description/comments.
• Application Owner (Director+) approval is given about the PR, and the approver is named in the description/comments.

👉 Regardless of which boxes you click in this comment, merge/deployment will not be blocked.
Reports about deployment policy adherence will be circulated daily.