APS.NET Core App Deployment to AWS Elastic Beanstalk on linux

**Describe the bug**
Deployment delete previous deployed version, if the new version fail to run, rollback is now not possible which leaves the beanstalk without a working version and new deployment is not possible due to version conflict. it takes work around to get the beanstalk running again.

**To Reproduce**
1. create a .net web api
2. use away tool to "publish to aws"
3. publish to new target
4. select "ASP.NET Core App to AWS Elastic Beanstalk on linux"
5. publish the application twice, and there will only be 1 version in the "application versions"

**Toolkit Logs**

**Development System (please complete the following information):**
- Windows Version: windows 11 24H2
- Visual Studio Version: 2022 17.14.16
- AWS Toolkit for Visual Studio Version: 1.78.0.0

Start by reproducing the deployment using the listed steps for “ASP.NET Core App to AWS Elastic Beanstalk on linux,” publishing twice and observing the application versions. Trace the publish-to-AWS deployment entry point and verify that a failed new deployment leaves the previous working version available for rollback and does not cause a version conflict on the next deployment.

Written by the indexing model from the issue text.