Changing Elastic Beanstalk instance type does not work

- Attached image shows which dropdown I'm using to change instance size.
- Also attached my deploy config. Notably I want to point out that this is a Single Instance config because I have a different set of bugs I want to file for Multi Instance config.
- Should be reproducible with an empty .NET Core Web App project

Any attempts to change instance type with the AWS Toolkit does not work. After hitting Apply, Elastic Beanstalk goes through its process of instantiating a new instance with the new instance type. However, after that process is done, you'll see that no changes have been made and the newly created instance is the original instance type.

Below is the EB trace when the Apply button is clicked

00 | INFO | Removed instance 'i-0da72d2f29101a136' from your environment. (Reason: Instance is in 'terminated' state)
-- | -- | --
2020-04-09 10:21:14 UTC-0700 | INFO | Adding instance 'i-07aa33b2ea7752ed0' to your environment.
2020-04-09 10:21:14 UTC-0700 | INFO | Environment health has transitioned from RED to GREEN
2020-04-09 10:21:14 UTC-0700 | INFO | Added EC2 instance 'i-07aa33b2ea7752ed0' to Auto Scaling Group 'awseb-e-gtrvdupfcm-stack-AWSEBAutoScalingGroup-OX18TICEV0VP'.
2020-04-09 10:20:44 UTC-0700 | WARN | Environment health has transitioned from GREEN to RED
2020-04-09 10:20:43 UTC-0700 | INFO | Environment update completed successfully.
2020-04-09 10:20:43 UTC-0700 | INFO | Successfully deployed new configuration to environment.
2020-04-09 10:20:07 UTC-0700 | INFO | Created Auto Scaling launch configuration named: awseb-e-gtrvdupfcm-stack-AWSEBAutoScalingLaunchConfiguration-8F09GGO87VV3
2020-04-09 10:19:51 UTC-0700 | INFO | Updating environment EBLabA-prod's configuration settings.
2020-04-09 10:19:46 UTC-0700 | INFO | Environment update is starting.

[ebconfig.txt](https://github.com/aws/aws-toolkit-visual-studio/files/4457701/ebconfig.txt)

Reproduce the issue with an empty .NET Core Web App, the AWS Toolkit instance-type dropdown, and the supplied ebconfig.txt. Compare the selected type with the replacement instance and the Elastic Beanstalk trace after Apply. Done means the new instance uses the requested type and the behavior is covered by an appropriate regression test.

Written by the indexing model from the issue text.