Synchronous commands give users better feedback and developer experience and other improvements

**Community Note**
* Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request

**Tell us about your request**

### Synchronous commands

I would like that - if I create a service with `aws apprunner create-service --cli-input-json "`cat`" ....`, the command exits when the service is actually created (or when the creation failed).

Same for starting a deployment with `aws start-deployment --service-arn `

This way, when my CI completes, based on the status of the CI I can immediately understand if the creation of the service (or the deployment) actually completed successfully or not.

Without this, developer experience degrades: indeed, either I have to find out which other commands to run to get a status update (ruining my ci code), either I need to visit the aws console to understand the status of the deployment.

### Provide only one command to deploy a service (create it if it does not exists, or update it)

I would like to have only one command that does both:
- create a service
- start deployment

This way my ci can launch only one command, it does not matter if the service exists or not. This would make my developer experience better (less commands, less knowledge needed, easier to get started, easier to setup new services)

## Describe alternatives you've considered

Google Cloud Run