v2.1.0: Stripe webhooks, authorization, and multiple deployment improvements, bug fixes

This release adds support for:

• Multiple deployments with different vendor prefixes on a single AWS account. This is useful for the development of multiple apps within a single AWS account.
• Support for specifying a tenantId claim in the access tokens and using them for making the authorization decisions. This allows tokens created using yarn ops jwt -c tenantId=... to impersonate a given tenant of the system and is useful for testing. NOTE Relying on this feature for customer support activities is a bad security practice.
• Support for distinct URLs for test and production Stripe webhooks.

Bug fixes:

• Improved documentation for setting up AWS CLI credentials (thanks @mauricioschneider).
• Fix the URLs in the samples within the documentation (thanks @ondrej).
• Improve error messages for LetsGo CLI commands that accept a choice of artifacts as an option.
• Fix #14. Enable building LetsGo Docker images on Apple silicone machines. (thanks @mauricioschneider).
• Fix #17. Adjust IAM permissions to allow the worker to enqueue subsequent work for itself.
• Fix #18. Fix the expiry time of the access token created for the worker to avoid a race condition in calling the HTTP API from within the worker.

v2.0.0: Scheduled tasks and shadcn/ui web components

This release adds support for:

• Scheduled tasks. With scheduled asynchronous tasks, the worker component can execute your custom code in the background on a schedule. This is useful for integration scenarios and internal data cleanup, among others. Read more in Scheduled asynchronous work.
• shadcn/ui. The web component now introduces a dependency on the shadcn/ui component library, which provides a healthy balance between utility and flexibility to customize the look & feel of your UI. Read more in Develop the frontend.

Bug fixes:

• Fix #10. The DynamoDB client now uses the correct AWS region.

v1.0.0: First release

The first release of LetsGo contains support for:

• web component based on Nextjs with App Router running in AWS AppRunner.
• API component based on Node.js with Express running in AWS AppRunner.
• worker component based on Node.js function running in AWS Lambda behind AWS SQS Standard Queue.
• database component with a simple data model deployed as an AWS DynamoDB table.
• devops CLI that supports managing multiple independent deployments of LetsGo across AWS regions and accounts.
• Auth0 integration to authenticate web users and protect API access.
• Stripe integration to support subscription-based pricing models.