[Feature/Bug] Pulsar 4.0.x incompatible with milvus-helm 5.0.x — bookkeeper.conf and OTEL config not updated for 4.x class paths

[chands08]

Environment

• milvus-helm chart version: 5.0.23
• Pulsar image tested: apachepulsar/pulsar:4.0.13
• Kubernetes: EKS (AWS)
• Milvus version: 2.6.19

Problem
Upgrading the Pulsar image tag to any 4.0.x release causes two independent CrashLoopBackOff failures:

1. Bookie — ClassNotFoundException:
   org.apache.bookkeeper.stats.prometheus.PrometheusMetricsProvider
   Root cause: class path was renamed to
   org.apache.pulsar.metrics.prometheus.bookkeeper.PrometheusMetricsProvider
   in Pulsar 4.0.10 (ref: apache/pulsar PR #1868). Chart's bookkeeper.conf still references old path.

2. Broker — Unrecognized value for otel.propagators: xray
   Root cause: AWS X-Ray OTEL propagator class was removed from Pulsar 4.x classpath.
   Chart's broker OTEL config still expects it.

Impact
Pulsar 3.0.x LTS reached security EOL on May 2, 2026 (36-month window from release).
CVE-2026-45447 (OpenSSL heap use-after-free, USN-8414-1, June 9 2026) cannot be
remediated on 3.0.x. The only supported Pulsar LTS with a patched OpenSSL base
image is 4.0.x (supported through October 2027).

Ask

1. Update bookkeeper.conf statsProviderClass to the Pulsar 4.x class path
2. Update broker OTEL config to drop or make xray propagator optional
3. Publish an official compatibility statement for Pulsar 4.0.x with milvus-helm 5.x