feat: add Terraform infrastructure-as-code configuration

[Christopherdominic]

• Create VPC module with public/private subnets across 2 AZs
• Add RDS PostgreSQL module with automated backups
• Add ElastiCache Redis module with automatic failover
• Create ECS Fargate module for container orchestration
• Add ALB module for traffic distribution
• Configure S3 backend with DynamoDB locking
• Add GitHub Actions workflow for terraform plan/apply
• Document setup and usage in README

Closes #105

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Dependency update
• CI/CD improvement

Related Issues

Closes #

Testing

• Unit tests added/updated
• Integration tests added/updated
• E2E tests added/updated (if applicable)
• Manual testing performed

Documentation

• README updated (if applicable)
• API documentation updated (if applicable)
• Code comments added for complex logic
• Migration guide added (if breaking changes)

Breaking Changes

• No breaking changes
• Breaking changes documented below:

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests passed locally with my changes
• Any dependent changes have been merged and published

Screenshots (if applicable)

Additional Context

[drips-wave]

@Christopherdominic Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits