Aborting acms:install leaves code changes to project that cause failures when trying to run acms:install again

[lauriii]

If acms acms:install exists without completing after it has modified composer.json, the project is left in a corrupted state because the command leaves code changes in place that prevent running the command again. In practice this prevents running acms acms:install again after aborting acms acms:install before completion.

Steps for reproducing

1. Create new ACMS project and require ACMS starterkit
2. Run ./vendor/bin/acms acms:install and select Acquia CMS Headless
3. Complete CLI steps until Mysql settings and abort command
4. Run ./vendor/bin/acms acms:install again and select Acquia CMS Headless
5. Complete CLI steps until the composer step. The CLI tool should fail to execute the composer commands.