The "waypoint server install -platform=ecs" should create HTTP target group with protocol TLS:9702 instead of TCP:9702 to allow custom domain with SSL

[thangnc]

Describe the bug
The waypoint server install -platform=ecs command always create the HTTP target group with protocol TCP. This leads we can not add the Network Load Balancer listener from TLS protocol to this HTTP target group. So, we can not route the custom domain with SSL certificate to Waypoint server.

This bug maybe caused from serverinstall/ecs.go#L1338

Steps to Reproduce

• Run waypoint server install command

waypoint server install -platform=ecs \
  -ecs-region="ap-northeast-1" \
  -ecs-subnets="subnet-a, subnet-b, subnet-c" \
  -accept-tos

• Go to EC2 > Load balancers > waypoint-server-nlb, there is a listener TCP:9702
• Go to EC2 > Target groups > waypoint-server-http, the detail shows Protocol:Port is TCP:9702
• Try to update waypoint-server-nlb listener from TCP:9702 to TLS:443, keep forwarding to waypoint-server-http target group
• Go to Route 53 > Hosted zones > cc-waypoint.example.com, add 1 more record to map to waypoint-server-nlb
• Run curl -v -L https://cc-waypoint.example.com:443 or open browser with URL https://cc-waypoint.example.com:443, it show the error Client try to send HTTP request to HTTPS server

Expected behavior
The waypoint server install command should allow TLS: 9702 when create new HTTP target group. By this way, we can map the custom domain with SSL certificate.

Waypoint Platform Versions
Additional version and platform information to help triage the issue if
applicable:

• Waypoint CLI Version: CLI: v0.11.2 (0759b76)
• Waypoint Server Platform and Version: ecs Server: v0.11.3

Additional context

• When i tried to create new target group with protocol TLS:9702 and register ECS container waypoint-server to this target group. I can hit the custom domain with SSL certificate.