Add hatch_jupyter_builder

[blink1073]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (hatch-jupyter-builder) and found some lint.

Here's what I've got...

For hatch-jupyter-builder:

• Please do not delete the example recipe found in recipes/example/meta.yaml.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/hatch-jupyter-builder) and found it was in an excellent condition.

[blink1073]

@Zsailer are you okay with being added as a maintainer?

[Zsailer]

👍

[blink1073]

@conda-forge-admin, please ping team

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/staged-recipes and so here I am doing that.

[blink1073]

Thanks @ocefpaf!