Create a pipeline to deploy MudMuseum website to S3 on changes

[nswarner]

When changes are pushed to MudMuseum website GitHub repository, use an action to trigger a pipeline to pull the changes and deploy them to the mudmuseum.com S3 bucket.

Requires some planning around:

• [x] Understand how GitHub actions can facilitate this event
• [x] Decide on the appropriate CICD tool (i.e. CircleCI, AWS Code*, GitHub Actions, ???)
• [x] Appropriate AWS IAM permissions to access S3 to deploy the website

[nswarner]

Created GitHub Actions pipeline to deploy the website when new changes are pushed to the MM-Website repository. Integrated with new IAM User that has restricted permissions of putObject into the mudmuseum.com bucket. Setup credentials via GitHub Secrets. Will need to decide on a key rotation policy in the near future. Tested and verified deploy works. Outstanding issue: CloudFront cache is invalidated once every 24 hours - may want to add a cache invalidation call to the pipeline (1,000 free invalidations per month, $0.005/invalidation afterward) OR create a new CloudFront cache policy that invalidates more frequently.