Added docker deployment

[kurtisassad]

Link to Issue

Closes: #9085
Closes: #9158

Description of Changes

• Refactors Dockerfiles to be compatible with the heroku docker deploys
• Adds datadog to Dockerfile.web (corresponds to our app)
• Adds deployment CD pipeline
• Adds dockerfiles for snapshot listener + discordbot

Test Plan

• Changed frack to use container deployments (step 1 of deployment plan)
• Merged this branch into the frack branch which makes a deployment to commonwealth-frack
• CAed around app
• Checked that knock notifications work correctly

Deployment Plan

1. When ready, first switch the heroku app from regular deploys to container deploys (heroku stack:set container -a commonwealthapp)
2. Make a PR into production branch. After this is merged it will be deployed to heroku. This will be our new deployment process.

Other considerations

• We need to do load testing. I needed to remove the get-max-old-space-size.sh because the docker image does not have information about the machine it is running on, and as a result it will fail. I suggest we do things the other way, instead of sizing the docker container to fit the dyno, we just use a dyno that will fit the docker container, and scale horizontally

[rbennettcw]

Did we decide that the max old space script is still needed? If so, perhaps it could be chained here at the RUN declaration? e.g. ./get-max-old-space-size.sh && ./datadog-entrypoint.sh

[kurtisassad]

We can't use the get-max-old-space-size because the docker container does not know at image build time how much memory the container has.

[rbennettcw]

I'm not talking about container build time, but rather container runtime, during the RUN step.

[rbennettcw]

Oops, for some reason I thought that was the entrypoint 😅

What I meant was the CMD step in the other dockerfiles. Nonetheless, LGTM– tweaks can be made later.

[Rotorsoft]

LGTM, just wondering if anything changes after @timolegros finishes work merging discord bot