Environment Configuration Options Missing from 'Publish To AWS' for Elastic Beanstalk

**Describe the bug**
There are numerous configuration options missing from 'Publish to AWS' for Elastic Beanstalk that require the environment be completely rebuilt or, when an initial deployment fails, leaves the user unable to reconfigure the environment via the Console to remedy if the environment is not in a 'Ready' state.
It would be helpful if these options were available in the AWS Toolkit UI when initially configuring an environment
1) Load Balancer Options: these changes require the recreation of a load balancer and therefore a new environment to change and aren't currently available in the AWS Toolkit UI
- Internal vs Public
- Shared vs Dedicated Application Load Balancer
2) Instance log streaming to CloudWatch logs
- Log streaming: if there is an issue with an initial deployment and the user is unable to see the logs, he can't determine the root cause to resolve and can't turn this option on when the environment is not in a 'Ready' state

**To Reproduce**
1) Publish an Elastic Beanstalk environment through the 'Publish to AWS' context menu. During configuration, if you need to configure your Load Balancer to be internal or shared, you cannot. If you try to change these settings through the console you receive the error:
Updating Load Balancer listener named: arn:aws:elasticloadbalancing:xxxxx failed Reason: Resource handler returned message: "The following target groups cannot be associated with more than one load balancer: arn:aws:elasticloadbalancingxxxx (Service: ElasticLoadBalancingV2, Status Code: 400,..)" (HandlerErrorCode: ServiceLimitExceeded). Currently if you need these options you can't use the tool.
2) Publish an Elastic Beanstalk environment through the 'Publish to AWS' context menu. If there are any errors with the application deployment the environment configuration will complete, but the environment will be in a Severe state since the health check fails. At that point the only diagnostics to determine the root cause would be in the application logs. However, you cannot turn on Cloudwatch log streaming in the Console because the application is not in a 'Ready' state. In my case there was a dll that didn't work on the linux deployment and caused the application to fail during loading.

**Expected behavior**
These settings are available through the 'Publish to AWS' UI since they directly impact the user's ability to configure the initial environment.

**Development System (please complete the following information):**
- Windows Version: Windows Server 2022
- Visual Studio Version: Visual Studio 2022
- AWS Toolkit for Visual Studio Version: 1.48

Start by reproducing the issue through the “Publish to AWS” context menu for an Elastic Beanstalk environment. Compare the configuration flow with the requested internal or public load balancer, shared or dedicated load balancer, and CloudWatch log streaming options; done means these settings are available during initial environment configuration.

Written by the indexing model from the issue text.