feat: Implement OIDC for secure CI/CD and centralize AWS configuration

[Hectormalvarez]

This pull request introduces significant enhancements to our deployment pipeline, focusing on security, maintainability, and automation for both development and production environments.

Key Changes & Improvements:

• Migrated to OIDC for AWS Authentication:

  • Replaced long-lived IAM user access keys with secure, short-lived credentials obtained via OpenID Connect (OIDC) between GitHub Actions and AWS.
  • This significantly improves security by eliminating static secrets and adhering to AWS best practices for CI/CD authentication.
  • Includes the setup of the OIDC Identity Provider in AWS and a dedicated IAM role with a refined trust policy.

• Centralized AWS Configuration:

  • Removed hardcoded AWS domain, base domain, and hosted zone ID values from config.ts.
  • These sensitive configuration details are now securely sourced from GitHub Actions secrets and passed as environment variables to the build and deployment processes.
  • Enhances maintainability and prevents accidental exposure of sensitive information.
  • Added runtime validation in config.ts to ensure all required environment variables are present during build/deployment.

• Implemented Production Deployment Workflow:

  • Introduced a dedicated GitHub Actions workflow for deploying to the production environment.
  • The production deployment is triggered upon merging pull requests into the main branch, promoting a controlled release process.

Why these changes were made:

• Security: Transitioning to OIDC drastically reduces the risk associated with compromised static AWS credentials.
• Maintainability: Centralizing configuration in GitHub Secrets simplifies management and ensures consistency across environments without modifying code.
• Automation: Automating the production deployment process ensures faster and more reliable releases after successful development cycles.

How to Test:

• Development Deployment: Push changes to the dev branch and verify that the deploy_dev workflow runs successfully and updates the development website.
• Production Deployment: Merge a pull request into the main branch and verify that the deploy_prod workflow runs successfully and updates the production website.
• Confirm that both deployments are utilizing the new OIDC authentication method and correctly reading environment variables for AWS configurations.