Translate awsentity processor last when translating pipelines

[phugay]

Description of the issue

• This PR is to make sure awsentity processor to be last in pipelines to consume necessary data from the previously added processors.

Description of changes

• For example, currently there could be a discrepancy where the ASG is in the appsignals metrics/logs, but it may not appear in compass. With putting awsentity processor last, we can leverage the tags retrieved from the resourcedetection processor to populate ASG for entity when appsignals is enabled.

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

• Modified a couple of existing unit tests
• Verified nothing changes on EC2 as this change is specific to k8s.
• Verified on EKS cluster by deploying my image, putting comparison logs below:

With default image on cluster:

before adding my image:

service:
    extensions:
        - awsproxy/application_signals
        - agenthealth/traces
        - agenthealth/logs
        - entitystore
        - server
    pipelines:
        metrics/application_signals:
            exporters:
                - awsemf/application_signals
            processors:
                - metricstransform/application_signals
                - awsentity/service/application_signals
                - resourcedetection
                - awsapplicationsignals
            receivers:
                - otlp/application_signals
        metrics/containerinsights:
            exporters:
                - awsemf/containerinsights
            processors:
                - metricstransform/containerinsights
                - gpuattributes/containerinsights
                - batch/containerinsights
            receivers:
                - awscontainerinsightreceiver
        traces/application_signals:
            exporters:
                - awsxray/application_signals
            processors:
                - resourcedetection
                - awsapplicationsignals
            receivers:
                - otlp/application_signals

With my image on cluster:

service:
    extensions:
        - awsproxy/application_signals
        - agenthealth/traces
        - agenthealth/logs
        - entitystore
        - server
    pipelines:
        metrics/application_signals:
            exporters:
                - awsemf/application_signals
            processors:
                - metricstransform/application_signals
                - resourcedetection
                - awsapplicationsignals
                - awsentity/service/application_signals
            receivers:
                - otlp/application_signals
        metrics/containerinsights:
            exporters:
                - awsemf/containerinsights
            processors:
                - metricstransform/containerinsights
                - gpuattributes/containerinsights
                - batch/containerinsights
            receivers:
                - awscontainerinsightreceiver
        traces/application_signals:
            exporters:
                - awsxray/application_signals
            processors:
                - resourcedetection
                - awsapplicationsignals
            receivers:
                - otlp/application_signals

Can successfully see the order change as expected.

Requirements

Before commit the code, please do the following steps.

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

[lisguo]

Unit tests might fail...we want to update the yamls too -

amazon-cloudwatch-agent/translator/tocwconfig/sampleConfig/appsignals_and_eks_config.yaml

Line 1259 in d6e36e5

- awsentity/service/application_signals

[Paramadon]

LGTM!