Same version ARC adoption and developer deployments are broken in 6.0.0

[BMurri]

Describe the bug
When running a same-version update in 6.0.0 the deployer ignores the AcrId, GitHubCommit, and SolutionDir configuration inputs and does not configure an ACR nor does it replace any of the service images.

Steps to Reproduce
Steps to reproduce the behavior:

• Scenario 1:

  1. Deploy 6.0.0 specifying TesImageName pointing to an ARC you already use. The deployer configures into "custom image" mode, and will warn about not providing updated TesImageName values in future upgrades.
  2. Rerun the deployer with the ArcId configuration.

• Scenario 2: Deploy 6.0.0. Clone the repo and make some changes. Rerun the deployer specifying SolutionDir.

In both cases, the configuration is ignored and no image build nor ARC configuration is performed.

Expected behavior
All three of those configuration values should follow the documentation and perform the same actions as when creating a deployment or updating a deployment with a newer version.

Deployment details: (any information you can provide would be helpful):

• OS: n/a
• Version: 6.0.0
• Any notable Azure customizations and/or configurations [e.g. Private Vnet, VM OS, ProvisionMySqlOnAzure = true]: no

Additional context
This problem also affects CoA. This problem has been fixed in the 6.1.0 beta