Add AMP as a metrics destination

[sky333999]

Description of changes

Introduce the ability to publish metrics to Amazon Managed Prometheus as a destination. Key highlights:

• Add metrics_destinations under metrics section of the agent config. The two supported destinations are cloudwatch (default if unspecified) and amp.
• amp destination requires the workspace_id as a required input. The remote write endpoint is built using a regex on top of the workspace ID.
• Leverages the prometheusremotewriteexporter to publish metrics to AMP.
• Attaches the sigv4authextension to sign API calls made to AMP using AWS credentials.
• Extract rollup_dimensions and drop_original_metrics functionality into a new processor that can be applied to non-cloudwatch destinations.

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

Manually tested changes on an EC2 to publish cpu metrics to AMP.

Requirements

Before commit the code, please do the following steps.

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

[github-actions[bot]]

This PR was marked stale due to lack of activity.

[github-actions[bot]]

This PR was marked stale due to lack of activity.