[improve][build] Upgrade OpenTelemetry libraries to 1.66.0 level - #26756

Motivation

Update the OpenTelemetry dependency families together, including the alpha modules already used by Pulsar, while preserving its JMX-only runtime metrics configuration.

Modifications

• SDK/API/BOM/exporters: 1.65.0 → 1.66.0, including matching alpha modules.
• Instrumentation: 2.30.0 → 2.31.1, including matching alpha modules.
• Semantic conventions: 1.43.0 → 1.44.0.
• GCP resources catalog entry: 1.59.0-alpha → 1.60.0-alpha.
• Update server and shell binary-license inventories.
• Remove the deleted Internal.setDisableAllJfrFeatures call. In the updated runtime telemetry builder, JFR stays disabled when no JFR metric selector is configured; Pulsar continues enabling only experimental JMX metrics.

Compatibility review against Pulsar usage:

• Instrumentation 2.31.0 changes the runtime telemetry selector API, addressed above. Pulsar does not use the removed declarative-config bridge or rely on its library instrumentation compile-classpath exposure of incubator APIs. 2.31.1 restores Spring Boot semantic-convention compile dependencies, which Pulsar does not use.
• SDK 1.66.0 renames declarative-config model setters; Pulsar uses programmatic autoconfiguration instead. Its Prometheus unit changes affect KBy, kBy, and TiBy, none of which Pulsar declares in its metrics.
• Contrib 1.60.0 removes EventToSpanEventBridge, which Pulsar does not use. Semantic conventions 1.44.0 compiles with the existing usages.

Instrumentation 2.31.1 targets SDK 1.65.0 upstream; Pulsar explicitly aligns the SDK to 1.66.0. Runtime compatibility remains subject to CI coverage.

Verifying this change

• Make sure that the change passes the CI checks.

help assemble sanityCheck checkBinaryLicense passed with configuration cache enabled, including main/test compilation and Checkstyle/Spotless. Tests are deliberately left to CI.

Does this pull request potentially affect one of the following parts:

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment