☁️🌳 Make Vonage archive setup easier

[rossng]

What's [new / improved / fixed]

• Auto-generate a VonageUser as part of the AWS stack, with limited privileges to read/write call archives.
• Update documentation to explain how to use this.
• 📦 Update CDK packages

Details

Upgrading

Instructions for other developers on how to upgrade their environment after pulling this new code. Please tick (i.e. put an 'x' in) the boxes for the actions that are necessary.

• [ ] Run GraphQL Codegen in the [frontend/actions service/playout service/realtime service]
• [x] Re-install NPM packages in /aws
• [ ] Apply Hasura migrations
• [ ] Apply Hasura metadata
• [ ] Update Auth0 rules
• [ ] Update environment variables
• [x] Re-deploy AWS CDK [and update AWS environment variables]

Deployment

Instructions for how to deploy these changes to production. Please tick (i.e. put an 'x' in) the boxes for the actions that are necessary.

• [ ] Apply migrations to Hasura
• [ ] Apply metadata to Hasura
• [ ] Reload enum table/values in Hasura for [table names]
• [ ] Re-deploy frontend
• [ ] Re-deploy actions service
• [ ] Re-deploy playout service
• [ ] Re-deploy real-time service
• [ ] Flush real-time service state (Redis/RabbitMQ)
• [x] Update environment variables for /aws

Any other steps necessary to re-deploy?

• Add Vonage API key to relevant AWS envfile
• Redeploy AWS stack and use the new VonageUser access key for Vonage archive webhook (if desired)