Allow waiting for a deployment to complete using the CLI

**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
If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
When using manual deployment, it is currently only possible to start a deployment asynchronously, but not wait for it to complete, which is a useful feature to have for CI/CD pipelines, where a successful deployment may trigger follow-up jobs to execute.

**Describe alternatives you've considered**
I currently use a shell script that calls the AWS CLI and checks the status of the most recent operation.

```
#!/bin/bash
# repeatedly poll status of the last operation and wait for it to be a final status
# --max-results 1 ensures only the latest operation is returned
ARN=$1
echo "[wait-for-apprunner-deployment] ARN: $ARN"
STATUS=""
while [ "$STATUS" != "SUCCEEDED" ]
do
STATUS=$(aws apprunner list-operations --service-arn "$ARN" --max-results 1 --output json | grep -m 1 '"Status"' | sed 's/.*"Status": "\(.*\)",/\1/';)
echo "[wait-for-apprunner-deployment] STATUS: $STATUS"
if [ "$STATUS" != "PENDING" ] && [ "$STATUS" != "IN_PROGRESS" ] && [ "$STATUS" != "SUCCEEDED" ]
then
echo "[wait-for-apprunner-deployment] Deployment failed" 1>&2
exit 1
fi

# AppRunner deployments are slow... now use checking more frequently than 5 seconds
sleep 5
done

echo "[wait-for-apprunner-deployment] Deployment succeeded"
```

Credit for the original script goes to: https://gist.github.com/jared-christensen/a5ed20c6fb27539bce5fb351e7cccbd5

**Additional context**

**Attachments**

Start by reviewing the manual deployment CLI entry point and the AWS CLI list-operations behavior described in the issue. The request is complete when the CLI can wait for deployment completion and report success or failure for CI/CD follow-up jobs; no repository files or tests are named.

Written by the indexing model from the issue text.