Edge cases with customers exiting sandbox while CFN deployment is in progress

[Amplifiyer]

Environment information

N/A

Description

While sandbox is performing a CFN deployment (not hotswap) through CDK, customers can CTRL-C and not delete the sandbox letting the CFN deployment continue at the server end (We don't cancel deployments when customer exits sandbox)

Now if customer runs the sandbox again, sandbox detects that there is ongoing CFN deployment, print warning to the customer and wait for further changes from customers. At this point, if customers do not make any changes to their files, their amplifyconfiguration doesn't get updated. This is because sandbox after getting restarted, is no longer listening for events from the previous deployment. This gets remedied automatically if customer makes any change after the previous deployment finishes.

There are few things we can do here:

1. Update the error message to let customers know and direct them to use the generate client-config command.
2. Build mechanism to "connect" to the CFN deployment (net new CFN service poller) since CDK CLI doesn't connect (doesn't even fail or tell customers that a deployment is in progress and silently quits)