AGE-432 : ECS Debugging Workflow + Added support for ECS specific receivers

[bhogayatakb]

• Added scripts in package-tooling/ecs to debug faster with ECS agent
• Added support of awsecscontainerinsightsreceiver
• Updated VM Agent - Docker build workflow to build image of specific arch

[naman-jain-15]

/review

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 PR contains tests

🔒 Security concerns No. The PR introduces debugging tools and scripts intended for development environments. While it exposes a Delve debugger port (2345) and uses public IPs for connection, these are explicitly documented as part of a manual debugging workflow and are not intended for production deployments. No secrets or sensitive credentials are hardcoded.

⚡ Recommended focus areas for review Incompatibility The sed command uses an empty string argument for the -i flag, which is a macOS-specific syntax. On Linux (GNU sed), this will cause an error or treat the next argument as the extension. This script is intended for developers who might be on different OSs. sed -i '' "s/\"host\": \"$OLD_IP\"/\"host\": \"$HOST_IP\"/" "$LAUNCH_JSON" Typo in Test The test checks for awscontainerinsightreceiver (singular 'insight'), but the actual component name in the OpenTelemetry collector is typically awscontainerinsightsreceiver (plural 'insights'). This might lead to false negatives in tests if the component name in the code doesn't match the string used in assertContainsComponent. assertContainsComponent(t, factories.Receivers, "awscontainerinsightreceiver") } else { assertNotContainsComponent(t, factories.Receivers, "awsecscontainermetrics") assertNotContainsComponent(t, factories.Receivers, "awscontainerinsightreceiver")