feat: ci pipeline

[The18thHuman]

Github actions pipeline of an angular app that involves docker image creation and publishing. This PR addresses the following task:

Test task

Pls open a github personal account if you don't have one. Pls fork the following repository (make it public) https://github.com/ganatan/angular-starter Inside that forked repo pls create Dockerfile based on an alpine image utilizing Nginx for the webserver. Pls create github actions (https://docs.github.com/en/actions) pipeline that will perform the following steps:

• run tests in that repository (if tests fail - send failure notification and stop the execution of the pipeline)
• run ng:build
• create a docker image based on your dockerfile with Nginx.conf && assets created by the step above (dist/angular-starter) inside the container
• store created docker image in the github packages, https://github.com/features/packages
• send email on success or failure to your personal email (if pipeline failed, for example, tests failed - you should send "fail" notification by email) Bonus step:
• measure the time for execution of your entire pipeline and send that info in the email notification. Once you polish your pipeline above, pls create docker-compose file that will run the produced docker image from https://github.com/features/packages on your local PC. Your result should be:

  docker-compose up
  curl localhost:8080

  that should output the entire HTML of the built angular application. The following new files should be added into the forked repository: .github/workflows/ci.yaml (your pipeline code)

• nginx.conf
• Dockerfile
• docker-compose.yaml No other files are allowed. Additional requirements for security: The produced container should start all the processes under "Nginx" user, no "root" process should be active inside the working container. If you have any questions - pls ask. When you are done - pls send a link to your solution (git repository).

[The18thHuman]

Thank you for your feedback! I understand the issues raised during the review and will address them in a timely manner. I appreciate your patience and attention to details. I will work on implementing the necessary changes as soon as possible.

[The18thHuman]

I wanted to bring up an issue I'm having with email notifications related to our pipeline. Currently, I don't have an email address configured that can send these notifications without hitting quota limits. This causes the pipeline to fail because I either cannot connect to my existing email provider or it returns an error that the send quota has been reached. I'd appreciate it if you could help me set this up.