[ECS] [request]: Add UDP_TCP protocol for container portMapping in the task definition

### 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 port mapping option for the containers currently supports TCP or UDP protocol. It should also have an option for protocol UDP_TCP. This would allow the same dynamic port to be assigned to the same container port over TCP and UDP.

**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?**
Currently, there is no option to map the same container port with different protocols. So, while trying to create a service behind an UDP Network Load Balancer the health checks fail as the health checks are done on TCP. If the UDP_TCP protocol is enabled then the same container port will be mapped to a single dynamic host port and would be helpful for application that serve traffic over both TCP and UDP.

**Are you currently working around this issue?**
Currently to solve this issue, a DAEMON service is also has to be deployed and the health check port of the NLB has to be changed to point to the daemon service port. The health check port has to be reverted back to "traffic-port" while updating the REPLICA service(behind the NLB) and then again the health check port is pointed to the daemon service port