Bug: jupyter server management is very brittle

The initial management of jupyter servers in
branch: dev/jlewi/jupyter
commit: c1b5319f799107f268a922707cf7de9bed10e95a

Is very brittle. The issue is we rely on token auth between the runme server and the jupyter server. The runme server then maintains a cache of the tokens/jupyter server configuration e.g. port. When starting jupyter server we need to write a .json file to the .runme-agent/jupyter directory.

There is all kinds of brittleness in this initial design. A lot of the issues go back to the double hop
runme -> jupyter_server -> ipykernel.

This was discussed in the original design in #63.

Some options are

1. Get rid of jupyter_server and reimplement websockets -> zmq inside runme.
2. Get rid of runme and talk to jupyter_server directly

Could we use OIDC with Jupyter server?
https://jupyter-server.readthedocs.io/en/latest/operators/security.html#authentication-and-authorization

I think we'd need an IdentityProvider/Authorizer plugin to validate the JWT and authorize users based on it.

Start by reading the referenced design in #63 and commit c1b5319f799107f268a922707cf7de9bed10e95a on dev/jlewi/jupyter, then trace the token and configuration flow through .runme-agent/jupyter. Compare the listed Jupyter server alternatives with the proposed OIDC IdentityProvider/Authorizer direction; the issue does not define a concrete implementation or completion test.