docs migration - Deploying to AWS with Fargate, Vapor, and MongoDB Atlas

Source: documentation/server/guides/deploying/aws-copilot-fargate-vapor-mongo.md
Proposed disposition: Migrate
Proposed destination: server-guides/Sources/ServerGuides.docc/deploying/aws-copilot-fargate-vapor-mongo.md
Reviewer: @swiftlang/server-workgroup

Checklist

• Create a GitHub issue to track this migration
• Determine disposition (suggested: Migrate) and confirm destination
• Review source for accuracy against current AWS Copilot, Fargate, and MongoDB Atlas versions
• Translate Jekyll markdown to DocC markdown format
  • Remove YAML front matter
  • Convert any Jekyll callouts to DocC-style callouts
  • Verify all AWS Copilot CLI commands against current release
  • Verify Vapor and MongoDB Atlas integration steps
• Add article to ServerGuides.docc/Documentation.md under a "Deployment" topic group
• Run swift package generate-documentation --analyze --warnings-as-errors in server-guides/
• Preview locally with swift package --disable-sandbox preview-documentation in server-guides/
• Submit PR to this repository for server workgroup review
• After merge and publication: add redirect_to: in the swift.org source file's front matter
• Submit redirect PR to swift-org-website

Start by reading documentation/server/guides/deploying/aws-copilot-fargate-vapor-mongo.md and compare it with the target server-guides/Sources/ServerGuides.docc/deploying/aws-copilot-fargate-vapor-mongo.md location. Translate the content, verify the AWS Copilot, Fargate, Vapor, and MongoDB Atlas steps, add it to Documentation.md, then run the documented generation and preview commands; done means the migration builds without warnings and previews correctly.