[Proposal] Rename to `hatch-jupyter`

[timkpaine]

Problem

This is the de-facto standard Jupyter build plugin for Hatch, but the name is a bit long 😅

Proposed Solution

Rename project and configuration sections to hatch-jupyter. This would also align with the emerging pattern:

• OP: https://github.com/ofek/hatch-containers
• OP: https://github.com/ofek/hatch-autorun
• https://github.com/joshua-auchincloss/hatch-cython
• https://github.com/aka-raccoon/hatch-aws
• https://github.com/cav71/hatch-ci
• https://github.com/OldGrumpyViking/hatch-conda

Additional context

• I am happy to do the implementation.
• I proactively grabbed hatch-jupyter name and added @blink1073 as an owner (feel free to remove me).
• Will also require renaming/re-adding the conda repo.

[blink1073]

Hi @timkpaine! I personally do not think it is worth the disruption to existing users. We'd also have to update https://blog.jupyter.org/packaging-for-jupyter-in-2022-c7be64c38926.

[Zsailer]

In the Jupyter Server meeting today, we talked about this.

It was mentioned that we could make one last release of hatch-jupyter-builder that depends on the new "hatch-jupyter" with not version pin. That way, folks can still use the old name but it's pulling in the new package to do all the business. Add all kinds of deprecation warnings too.

I'm not sure it's worth the possible headache either, but don't have a strong opinion either way.