Implementing OtelJMX metrics exporter for JMX metrics insights

[mitali-salvi]

Issue #, if available:

Description of changes:

1. Implemented custom provider for OtelJMX metrics insights
2. Is enabled when AWS_JMX_ENABLED is set to true
3. Sets up a metrics exporter over 4314 port only over HTTP protocol

Testing
Tested as part of amazon-cloudwatch-observability helm-chart

1. Annotate a pod deploying a sprint boot project with instrumentation.opentelemetry.io/inject-java: "true" cloudwatch.aws.amazon.com/inject-jmx-jvm: "true" and deploy on the cluster
2. Deploy the helm-chart with a custom amazon-cloudwatch-operator build to inject the following environment vars

OTEL_EXPORTER_OTLP_PROTOCOL
OTEL_METRICS_EXPORTER
OTEL_LOGS_EXPORTER
AWS_JMX_EXPORTER_METRICS_ENDPOINT
OTEL_JMX_TARGET_SYSTEM

3. Verified AwsJMX exporter is enabled in pod logs

 INFO software.amazon.opentelemetry.javaagent.providers.AwsJMXMetricsCustomizerProvider - AWS JMX metric collection enabled

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[bjrara]

We need to verify how well works with Application Signals runtime metrics.

[bjrara]

Please update the PR with the verification result of the following test cases as there's no UT added for those changes:

1. OTEL_METRICS_EXPORTER is none, OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is not set -> no metrics are exported.
2. OTEL_METRICS_EXPORTER is none, OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is set, OTEL_JMX_TARGET_SYSTEM is jvm -> only JMX JVM metrics are exported to AWS JMX EP, no other metrics are exported.
3. OTEL_METRICS_EXPORTER is not none (e.g. logging), OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is set, OTEL_JMX_TARGET_SYSTEM is jvm -> only JMX JVM metrics are exported to AWS JMX EP, all metrics are exported to the default exporter, JMX JVM is dual published.
4. OTEL_METRICS_EXPORTER is not none (e.g. logging), OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is not set -> no metrics are exported to AWS JMX EP, all metrics are exported to the default exporter.
5. OTEL_METRICS_EXPORTER is not none (e.g. logging), otel.jmx.enabled is disabled, OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT is set, OTEL_JMX_TARGET_SYSTEM is jvm -> same as 4, except JMX JVM metrics are not exported to the default exporter.

[musa-asad]

1. Tested and it didn't emit any metrics as expected.

- env:
        - name: OTEL_METRICS_EXPORTER
          value: none

2. JVM metrics received:
   

- env:
        - name: OTEL_METRICS_EXPORTER
          value: none
        - name: OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT
          value: http://cloudwatch-agent.amazon-cloudwatch:4314/v1/metrics
        - name: OTEL_JMX_TARGET_SYSTEM
          value: jvm

3. JVM metrics received:
   Same as above.

We got errors in the logging to show it was trying to send metrics to the default OTLP exporter endpoint.

- env:
        - name: OTEL_METRICS_EXPORTER
          value: otlp
        - name: OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT
          value: http://cloudwatch-agent.amazon-cloudwatch:4314/v1/metrics
        - name: OTEL_JMX_TARGET_SYSTEM
          value: jvm

4. Same error and no metrics.

- env:
        - name: OTEL_METRICS_EXPORTER
          value: otlp
        - name: OTEL_JMX_TARGET_SYSTEM
          value: jvm

5. Same error and no metrics like above.

- env:
        - name: OTEL_METRICS_EXPORTER
          value: otlp
        - name: OTEL_JMX_ENABLED
          value: "false"
        - name: OTEL_AWS_JMX_EXPORTER_METRICS_ENDPOINT
          value: http://cloudwatch-agent.amazon-cloudwatch:4314/v1/metrics
        - name: OTEL_JMX_TARGET_SYSTEM
          value: jvm