[AWS Fargate] Added support for DesiredStatus and KnownStatus for ECS Tasks

[girodav]

What does this PR do?

This PR adds DesiredStatus and KnownStatus among the collected metrics for ECS Fargate. The values are collected at the task level, not at the container level. More info at: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-metadata-endpoint-v4.html

Related PR for beats elastic/beats#32342

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

To test the end-to-end data flow, the easiest approach involves running amazon-ecs-local-container-endpoints and elastic-agent in two Docker containers on the same network (more info available at this blog post from AWS)

Related issues

• Closes [Metricbeat] [AWS Fargate] Include 'DesiredStatus' and 'KnownStatus' fields with module/agent integration #3576

[zmoog]

LGTM!

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-07-26T09:41:09.839+0000

• Duration: 14 min 30 sec

Test stats 🧪

Test	Results
Failed	0
Passed	11
Skipped	0
Total	11

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (0/0)	💚
Files	100.0% (0/0)	💚 2.901
Classes	100.0% (0/0)	💚 2.901
Methods	66.667% (2/3)	👎 -22.665
Lines	100.0% (0/0)	💚 9.423
Conditionals	100.0% (0/0)	💚