Move jupyter_builder_hatch plugin to jupyterlab org

[blink1073]

Problem

Jupyter Packaging has several limitations due to being tied to setuptools, which has a lot of legacy code and is under-maintained. setuptools has lagged far behind the PEP standards regarding packaging backends.

cf jupyter/jupyter-packaging#145 for more background.

Proposed Solution

• Hatch is a newly minted pypa project, and appears to be a drop-in replacement for our use of setuptools / jupyter-packaging. Hatch has also recently had a 1.0 release, and the primary author has been extremely responsive and interested in our successful use of hatch.

• Use a new hatch_jupyter_builder plugin as a drop-in replacement for jupyter_packaging in the places we are currently using it (e.g. cookiecutters, jupyterlab, and notebook). There is a proof of concept PR already in progress: Use hatch backend jupyter/notebook#6425

• Move hatch_jupyter_builder from my org to the jupyterlab org because it will primarily be used by jupyterlab, allowing it to fall under Jupyter governance. We could later decide to move it to the jupyter org as other parts of the ecosystem (such as widgets) start to use it.

[fcollonval]

Thanks a lot for doing this @blink1073
I'm 👍 for migrating the repo in JupyterLab org

[blink1073]

I plan to move this early next week if there are no strong objections.

[blink1073]

Done! Next steps are outlined in jupyterlab/jupyterlab#12606