Bundle the configproxy

[rgbkrk]

In the same way that jupyterhub launches the configproxy in the same container, we should do that here as well to make operations simpler.

[parente]

If both processes are in the same container, what would the container entrypoint (PID 1) be?

[rgbkrk]

tmpnb / orchestrate.py. This is what JupyterHub does. I liked having it broken out personally, but it seemed like people had trouble with running multiple services.

[parente]

I like having it broken out too, but I don't have an argument against combining to one container in light of the fact that the CHP does not retain state after a restart. If it did, then I'd suggest it remain separate, or at least separable.