Use change set to deploy changes after new release

[hannah-sun]

What does this PR do?

• replaces update-stack with create-change-set and execute-change-set so users can apply changes to macro upon new release
• modifies create_test_stack and update_test_stack scripts (used for testing) to use change sets to update stack
• adds simplified template for quick testing; can deploy without the zip copier method that's used to distribute to customers (usage for test scripts and simplified template documented on wiki page)

Motivation

The update-stack cli method does not create a change set for the CloudFormation stack, so customers will not be able to get the changes we've made in new releases based on the current instructions. To make sure changes are deployed, users will need to create and execute a change set instead.

Testing Guidelines

Used scripts ./tools/create_test_stack.sh and ./tools/update_test_stack.sh to test new method of updating with change sets.

Types of changes

• [x] Bug fix
• [ ] New feature
• [ ] Breaking change
• [x] Misc (docs, refactoring, dependency upgrade, etc.)

[hannah-sun]

Turns out update-stack works to make resource changes, but just doesn't provide change sets to preview changes, closing this now