Relocate ./contrib to a new github repository like jupyterhub/jupyter-server-proxy-contrib?

[manics]

https://github.com/jupyterhub/jupyter-server-proxy/tree/v3.0.0-rc.1/contrib contains additional mini-python projects that aren't tested or published by our standard CI workflows. This has several consequences:

• Not tested!
• We've unified the release process for the Python jupyter-server-proxy and NPM @jupyterlab/server-proxy packages but contrib falls outside of this release process, and in any case they're independently versioned.
• If we did make changes to contrib they'd either appear in the CHANGELOG for jupyter-server-proxy even though they're not released as part of jupyter-server-proxy, or we'd have to manually remove them.
• If more projects are added to contrib in future this becomes even more complicated
• They're a bit hidden away, if you see this repo it's not obvious there are some hidden repos inside, maybe that's why there aren't many contributions?

How does everyone feel about moving the contents of contrib to a new repository jupyterhub/jupyter-server-proxy-contrib. Or do you have some other ideas?

[ryanlovett]

I'm in favor of putting the theia contribution into its own repo and then documenting it in the examples section. The code-server-traitlet could be reproduced entirely in the docs, or put in a gist and then linked to from the docs.