Set up CI/CD pipeline to build and deploy the frontend

[antoniolofiego]

There is currently no pipeline or deployment of the new frontend. To be able to work on both the front and backend, there needs to be a complete dev environment deployed incorporating both. The pipeline is very similar to the current cicd/codepipeline-dev.template.yaml template in the backend repo.

We should create two separate stacks for frontend and backend, given that all the interactions between the two rely exclusively on REST APIs.

[what-name]

• Deployment GitHub Action merged with #33 - it deploys the dev branch's contents into the dev bucket and CF distribution
• The current workflow does not invalidate CloudFront cache, TTL can be set to a minimum on the dev version in order to aviod having to manually invalidate it. It is not set like that currently, so please let me know what you think on that. (it's simple to change)
• There is no testing or linting in the workflow itself, should/could there be something?
• Resources (S3 bucket, CF distribution, IAM user who's access keys are being used, etc.) are deployed within the backend stack. Since we switched to GitHub Actions instead of CodeBuild, it is a much cleaner solution that avoids having to maintain and deploy a tiny template from this repo seperately.
• We should add a badge to the README to see if the deployment is failing or passing (it's always good to see that upfront)
• Here is the development CloudFront URL: https://d2tz5aklrov90y.cloudfront.net

[rishabkumar7]

@what-name Badge for the README can be used https://github.com/100DaysOfCloud/100DaysOfCloudFrontend/workflows/CICD-dev/badge.svg

[rishabkumar7]

Added the following 2 for now, we can discuss what all badges we need.