[ECS] [Service Connect Proxy Tracing Configuration]: Allow configuration of Service Connect Proxies via Supported Environment Variables

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
The ECS Service Connect agent appears to support tracing according to the [docs](https://github.com/aws/amazon-ecs-service-connect-agent) however it does not allow configuration when used with Service Connect, only when used with AppMesh.

> These environment variables can be configured when used with AWS App Mesh, and they are not configurable when used with ECS Service Connect.

I'd like to be able to configure some of these options when using service connect and ingest traces.

**Which service(s) is this request for?**
Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Traces allow for more rich observability on an ECS Cluster using Service Connect. Not having them feels like a missing feature.

**Are you currently working around this issue?**
Custom instrumentation of services in the cluster, but the picture is incomplete.