Option to specify S3 bucket to upload resource zip to

When trying to submit a new module via `cfn submit`, it fails as it tries to create a CFN stack which sets up an S3 bucket to upload the zip to, the `CloudFormationManagedUploadInfrastructure` stack. In my case it fails as it tries to set up a resource without a permissions boundary.

I tried updating the template to include the permissions boundary, which worked and the stack was created successfully, but when I then run `cfn submit`, it tries to update the stack to remove the permissions boundary, which again fails.

As I understand it, the only point of this stack is to have an S3 bucket to store the zip so it can be registered in CFN. As such, it would be useful if we could just provide the S3 bucket ourselves to the submit command so we can set up the bucket in whichever way necessary.

I have currently worked around this by running `cfn submit --dry-run` to get the zip file, then using the AWS CLI to upload to S3 and register the module.