create-cluster/destroy-cluster implement Config RFC

[chelma]

Description

As part of the work to implement the RFC for our revamped config handling (#80, #81), this task is the work to update create-cluster and destroy-cluster per the RFC. The steps should look something like:

* Create S3 bucket on `create-cluster`; destroy S3 bucket on `destroy-cluster`
* Create user config directory from master on `create-cluster`
* Code to tarball config/upload to s3/update param store; tag S3 and Param Store with `aws-aio` version(s)
* Update `create-cluster` to perform tarball upload if no existing config
* Update container config/logic to use tarball
* README update

Acceptance Criteria

• create-cluster sticks user config in s3 and container pulls it down and installs/runs it
• create-cluster does not update config if already deployed
• The aws-aio version(s) are tracked
• destroy-cluster removes the s3 bucket without needing to use the --destroy-everything flag
• README updated to explain how to make config changes

[chelma]

Acceptance criteria met; resolving