[IT-3975] Opentelemetry collector as a gateway

[BryanFauble]

Background:

1. One of the way to deploy an opentelemetry collector is as an ECS service (Gateway) for other services to access as described in this blog post: https://aws.amazon.com/blogs/opensource/deployment-patterns-for-the-aws-distro-for-opentelemetry-collector-with-amazon-elastic-container-service/

Problems to solve:

• How can we deploy the OTEL collector as a service to ECS Fargate
• How can we deploy multiple services to ECS and allow them to use AWS Service discovery to permit HTTPS traffic (https://github.com/Sage-Bionetworks/multi-services-ecs-demo/tree/dev POC work)
• How can we inject configuration securely and secretly as shown in this example with the oauth2client extension for the collector? (https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/oauth2clientauthextension) - One example described in https://aws-otel.github.io/docs/setup/ecs/config-through-ssm is to use the value of an environment variable set from AWS System Manager Parameters. Sage uses AWS Secrets manager, and per the documentation all that should need to be set is the AOT_CONFIG_CONTENT environment variable.