[ECS-Anywhere] [Service Discovery]: Add support for Service Discovery with ECS-Anywhere

### 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**
What do you want us to build?
Add support for Service Discovery with ECS-Anywhere

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
We want the ability to make API calls from a container in one ECS service to a container in another ECS service. Both ECS services running on ECS-Anywhere Cluster.

**Are you currently working around this issue?**
How are you currently solving this problem?
We can't do ECS-Anywhere without Service Discovery support.

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

The issue requests Service Discovery support for containers in separate ECS-Anywhere services. No files, tests, or implementation entry points are mentioned; begin by identifying the ECS-Anywhere and Service Discovery integration area. Done means enabling API calls between containers in the two services.

Written by the indexing model from the issue text.