Remove BraveX Sandbox Lambda Deployment Resources

[hspencer77]

Summary

Remove artifacts that deploy and maintain BraveX Sandbox Lambdas.

Type of Change

• Product feature
• Bug fix
• Performance improvement
• Refactor
• Other

Remove resources since BraveX is no longer an initiative.

Tested Environments

• Development/Sandbox
• Staging
• Production

[github-actions]

[puLL-Merge] - brave-intl/bat-go@2443

Description

This PR removes the serverless email service code from the bat-go repository. The motivation for this change is not provided in the PR diff, but it appears to be a code removal or cleanup.

Changes

Changes

• .github/workflows/sam-dev.yml: Deleted file that contained a GitHub Actions workflow for deploying the serverless email service to a development environment.
• serverless/email/Makefile: Deleted Makefile for building the serverless email service.
• serverless/email/README.md: Deleted README file describing the serverless email service.
• serverless/email/status/*: Deleted Go code and modules for an AWS Lambda function that handled email status notifications via SNS.
• serverless/email/template.yaml: Deleted AWS SAM template for deploying the serverless email service infrastructure.
• serverless/email/unsubscribe/*: Deleted Go code and modules for an API endpoint to handle email unsubscribes.
• serverless/email/webhook/*: Deleted Go code and modules for an API endpoint to handle incoming email webhooks.

Security Hotspots

1. High Risk: The deleted webhook code contained plaintext secrets (AUTH_TOKENS, AUTH_SECRETS) retrieved from AWS Secrets Manager. Ensure these secrets have been properly rotated since this code has been removed.

2. Medium Risk: The deleted webhook code implemented its own HMAC request signature validation. Verify that any clients of this webhook have removed their signing code as well to avoid broken integrations.

3. Low Risk: Confirm that removing this serverless email service does not unexpectedly break any other parts of the BraveX system that may have depended on its functionality.

In summary, the main security consideration is to ensure any secrets used by this removed code have been invalidated and rotated. The other risks are more around avoiding broken integrations and system failures from this code removal.

[evq]

🥲