Have a better message when the CI or another dev is already pushing to the cloud

### Is this related to a new or existing Amplify category?

_No response_

### Is this related to another service?

_No response_

### Describe the feature you'd like to request

When trying to do a push to Amplify but one is already in progress the push will fail with a cryptic message about "UPDATE_IN_PROGESS"


Its taken me a while to work out that this occurs when my CI is also deploying or if one of my team is also deploying manually. Setting up CI is often part of the "hey lets get you setup with Amplify" steps but its easy to forget about it as a lot of the other tutorials tell you to do a push.

Without the knowledge that this simply means "something else is already deploying please wait" it can cause some head scratching!

### Describe the solution you'd like

Show a better message when the "UPDATE_IN_PROGRESS" error comes back. Something along the lines of:

_It could be that your CI or another team member is in the middle of a deploy, check the Amplify Console to check or wait a while and try again._

With a nice link to the console if possible. Can we work our if they even have CI setup from the console I wonder? Could mean we could hide the CI part of the message if not.

### Describe alternatives you've considered

I'm not sure if it would be worth reminding users within the CLI that CI is configured and will kick in. For instance when trying to do a ``amplify push`` could we warn that:

"_you have CI setup for this solution, you can trigger that and get a deploy by just pushing your changes with git. Do you want to continue with a manual deployment [Y/n]_".

This should support/honour the ``amplify push -y`` param too.

### Additional context

_No response_

### Is this something that you'd be interested in working on?

- [ ] 👋 I may be able to implement this feature request
- [ ] ⚠️ This feature might incur a breaking change