To avoid having a full checkout of the Application that needs to be updated independently, we should use the atomic deploy facilities of the infrastructure repo, where the application that is deployed has "hooks" for certain events (like building, packaging, etc).

Benefits:

• More clear separation between code for deployment and application code
• More standardized approach to deployment
• Branches that need to provide new deployment steps can be tested without changes on the deploy server.

There is a PR that does this at https://github.com/wmde/FundraisingFrontend/pull/880, however, that one was created before we moved to Docker containers and calling them through the Makefile.

AC:

• FundraisingFrontend clone (in the home directory of the deploy user) is no longer used.
• There is a playbook for deploying the fundraising frontend in the deployments directory of the infrastructure repository. To avoid having this changing frequently, we could split the atomic deployment into a separate repository.