AWS credentials and S3 bucket must be updated for future use

[mradamcox]

If the data-pull workflow is ever reactivated, or the atlas is re-deployed from this repo, some work will need to be done to use the new bucket and AWS account that now holds the archive data.

1. A new set of CLI user credentials will need to be made in the Herop AWS account where the new bucket is located.
   • This user will need read/write access to the geoda-atlas-covid2 bucket.
2. Environment variables will need to be changed in this repo's settings to reflect these creds and the new bucket:
   • S3_DEPLOYER: access key for new AWS user (commonly called AWS_ACCOUNT_KEY_ID)
   • S3_DEPLOYER_KEY: secret access key for new AWS user (commonly called AWS_SECRET_ACCESS_KEY)
   • S3_BUCKET: geoda-covid-atlas2
3. The code base will need to be audited for direct references to the old geoda-covid-atlas bucket and changed to geoda-covid-atlas2