Adding Container Insights Jmx Pipeline

[Paramadon]

Description of the issue

We want to be able to have java/jmx container insights dashboards populated.

Pipeline overview

Reciever

1. otlp - jmx

Processors

1. Filter Processor - filters out any undesired metrics
2. Resource Detection processor - adds k8scluster and nodename to resource attributes
3. Tranform processor Removes any attribbutes that are not of the correct dimension for each metric: The dimension criteria is from here: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-metrics.html#ContainerInsights-Prometheus-metrics-jmx
4. Metric Tranform Processor - Renames all metrics to fit prometheus container insight dashboard

Exporters

1.. Debug exporter - Helps visualize which metrics are being created (can be removed)
2. Aws Emf Exporter - send metrics to Namespace: ContainerInsights/Prometheus (based off of documentation) with Log group name /aws/containerinsights/{ClusterName}/jmx and log stream name: {NodeName}. Both ClusterName and NodeName comes from the resource attributes.

Note one requirement for the Container Insight Java/Jmx dashboards to be populated is to have java_lang_operatingsystem_totalphysicalmemorysize metric. Without this metric the dashboard will not be populated.

Description of changes

How does this change address the problem?

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Tests

Created unit tests for each processor and tocwconfig test which test the full generated yaml from json. The test is called TestContainerInsightsJMX

Requirements

Before commit the code, please do the following steps.

1. Run make fmt and make fmt-sh
2. Run make lint

[sky333999]

We should update schema.json and the associated tests as well.