Update AWS S3/EC2 sync operations (#1290)

[Thistleman]

This PR will update/create the CI/CD workflow for syncing s3 and updating versions.gridlabd.us. This is a targeted CI/CD update that should be considered separately from the mass image generation and upload PR, as it deals with a much more specific issue and a significantly different potential process, which should not delay the other higher priority PR.

Current Issues

TODO

Code Changes

• [x] AWS S3 sync on cloud folders
  • [x] code.gridlabd.us
  • [x] docs.gridlabd.us
  • [x] geodata.gridlabd.us
  • [x] install.gridlabd.us
  • [x] status.gridlabd.us
  • [x] tutorials.gridlabd.us
  • [x] www.gridlabd.us
• [x] Upgrade version.gridlabd.us to serverless lambda queries
  • [x] Implement terraform to deploy lambda infrastructure
  • [x] Implement CI/CD to update lambda app.py as needed
  • [x] Change "version.gridlabd.us" endpoint to use api gateway endpoint in route53 and cloudfront
  • [x] Add route to update official latest version for master and develop routes
  • [x] Add security keys for update_latest routes
  • [x] Add route for logging and timestamp of version calls
  • [x] Add support for querying stats of all version calls, with system for additional grouping to be added later

Bug Fixes

None

Documentation Changes

Added README.md to version.gridlabd.us folder with instructions on using the terraform files and the lambda routes.

Test and Validation notes

(develop/master)-images.yml workflow is meant to only be used when merges are completed to their respective branches.

[dchassin]

Per @Thistleman, "failing post to s3 curl command in github actions is correct behavior. It is a 400 error as updates are only allowed for the develop and master branches."