Move acquisition deployment off of github-deploy-repo

[krivard]

github-deploy-repo works via a webhook. The webhook is written in PHP, which we are slowly scrubbing from Delphi's active tech stack.

This webhook silently broke after the v4 deployment. While we have developed a fix, a better long-term solution would be to change the deployment mechanism for the acquisition system to something that more closely matches the approaches used by all our other active projects.

[krivard]

Related:

• Infra refactor: convert acquisition to an installable package #939
• Get "secrets" from something other than the operations repo #965

[melange396]

it looks like the way tests are run by github-deploy-repo is not completely compatible with the way we do it in our current standard development cycle (see this slack thread for some context). if we do not completely move away from github-deploy-repo in the near future, we may consider removing its testing step(s), or at least be cognizant of the fact that they can be unreliable.

[melange396]

to sanitize https://github.com/cmu-delphi/github-deploy-repo from this repository, we should...

remove references to "github-deploy-repo" from:
https://github.com/cmu-delphi/delphi-epidata/blob/dev/.github/workflows/ci.yaml
https://github.com/cmu-delphi/delphi-epidata/blob/dev/dev/docker/python/setup.sh
https://github.com/cmu-delphi/delphi-epidata/blob/dev/dev/local/install.sh

remove references to "github_deploy_repo" from:
https://github.com/cmu-delphi/delphi-epidata/blob/dev/dev/local/setup.cfg

delete these two files:
https://github.com/cmu-delphi/delphi-epidata/blob/dev/deploy.json
https://github.com/cmu-delphi/delphi-epidata/blob/dev/integrations/test_deploy_syntax.py

and then do:

• get rid of "__test_target__" et al #1129

[melange396]

references to "undefx" probably can and should also be removed from the above files too

[korlaxxalrok]

For now we are still heavily reliant on github-deploy-repo to write the various parts of delphi-epidata (via deploy.json) to a filesystem so that the expected import locations and module paths work.

We also still use the webhook functionality, but only in production (and manually deploy to staging).

We can probably make it stop running tests since we do most of that already in Actions CI now, but we'll need to keep it around until we have a different way of getting our bits into an environment that can run them.

A good goal would be to containerize "everything" so that we can start looking at more flexible systems to host and run our jobs, as well as local development rigs and workflows.

[dshemetov]

This comment may be useful when refactoring our repo paths.