Summary:
This diff introduces the changes required to enable the OpenTelemetry Collector in the universe for exporting audit logs to cloud monitoring services such as Datadog, AWS CloudWatch, and others.

When enabled, the Yugabyte Helm chart will deploy an OpenTelemetry Collector (otel-collector) Custom Resource (CR). This CR configures the deployment (as a sidecar) of a collector container within the tserver pod. The collector container extracts audit logs from the tserver log file and forwards them to the exporter specified in the CR configuration.

This integration provides seamless observability and monitoring capabilities by leveraging the OpenTelemetry framework, allowing users to easily export and analyze audit logs in their preferred monitoring platform.

Test Plan:
Tested the following scenarios -

  # Create a 1RF 1node universe with otelCollector enabled
  # Create a 3RF 3node (multi-AZ) universe with otelCollector enabled
  # Create a 1RF 3node universe with otelCollector enabled
  # Create a universe with RR with otelCollector enabled
  # OtelCollector with multiple exporters (AWS, GCP, DD)
  # Ensured that the secretEnv values are base64 encoded

Reviewers: vkumar, anijhawan, sneelakantan, skurapati, amalyshev

Reviewed By: vkumar, amalyshev

Subscribers: amalyshev, yugaware

Differential Revision: https://phorge.dev.yugabyte.com/D41303