Clearly separate deployment target configurations

[kevinsmith]

Pledge
I plan to personally implement this enhancement.

Is your feature request related to a problem? Please describe.
We essentially have a several different deployment targets at play here: test in Docker, standalone test, prod in Docker, standalone prod, tor, railway. I can foresee more environments as well, like Gitpod, GitHub Codespaces, or additional "one-click deployments" like railway.

Describe the solution you'd like
Code organization that makes it clear which settings and configuration belong to which deployment target environment. If a deployment target were deleted from the codebase, we should be able to easily remove it without much fuss or unintended effects in the rest of the project.

Describe alternatives you've considered
Do nothing.

Additional context
N/A

[cameri]

Should I close #119 or can you incorporate it here?

[kevinsmith]

I think they're complimentary, but not necessarily the same enhancement. I'd keep them separate to avoid difficulty in one of them holding up the improvement in the other.