sam deploy ignores --s3-bucket option

### Description:
I was thinking it would be nice to have 1 bucket for aws sam deployments rather than several randomly named buckets "aws-sam-cli-managed-default-samclisourcebucket-xxxxxxx". If. you try to do --guided with --s3-bucket switch is ignored and it will create a randomly named bucket for you.

Also the ' --resolve-s3 ' switch makes reference to a '--s3-guided' switch that does not exist.

### Steps to reproduce:
sam deploy --guided --profile myadminprofile --s3-bucket SomeS3BucketNaneGoesHere

### Observed result:
SAM creates a bucket "sam-cli-managed-default-samclisourcebucket-xxxxxxx"

### Expected result:
SAM uses the bucket name i specify

### Workaround:
sam deploy --guided ....
sam delete
edit samconfig.toml with new s3 bucket name
sam deploy ...

### Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

1. OS: OSX 12.2.1
2. If using SAM CLI, `sam --version`: 1.40.1
3. AWS region: us-west-2