Health checks fail when using the new publish to elastic beanstalk interface

**Describe the bug**
Health checks fail when using the new publish to elastic beanstalk interface

**To Reproduce**
1. Right click project in Visual Studio
2. Click "Publish to AWS..."
3. Select existing application environment
4. Click "Publish"

**Expected behaviour**
Application should be deployed the same as legacy interface

**Computer (please complete the following information):**

- Windows Version: Windows 11 Pro build 22621.963
- Visual Studio Version: 17.3.5
- AWS Toolkit for Visual Studio Version: 1.38.0.0

**Additional context**
Deploying .NET 6 application to Amazon Linux 2/2.4.2. "Publish to AWS Elastic Beanstalk (Legacy)" works as expected. Health check simply checks for 200 from specific end point,. Using ELB type Application Loadbalancer. Environment has 5 instances of t3a.small and is part of a VPC. Uses rolling deploy based on health with batch size of 50%. Application version is successfully pushed to instances in first batch but instances are not re-registered with loadbalancer gets stuck on the step saying "Registering instance(s) with the load balancer and waiting for them to be healthy." Under "causes" in the console no error codes are shown.

Reproduce the deployment through Visual Studio's new “Publish to AWS...” flow using the reported .NET 6, Amazon Linux 2, Application Load Balancer, and rolling-deploy setup, then compare it with the legacy publish flow. Investigate the step where instances are registered with the load balancer and waiting for health, and consider the issue done when the new interface completes deployment and the endpoint returns 200.

Written by the indexing model from the issue text.