Create npe2.yaml to patch (remove) pydantic pin

[psobolewskiPhD]

In napari/npe2#321 the pydantic < 2 pin was dropped from npe2 but it was missed here, so the conda-forge package still requires pydantic 1.
0.7.3 and 0.7.4 shouldn't have pydantic upper bound.

See also: conda-forge/npe2-feedstock#20
closes: napari/npe2#343

Checklist

• Used a static YAML file for the patch if possible (instructions).
• Only wrote code directly into generate_patch_json.py if absolutely necessary.
• Ran pre-commit run -a and ensured all files pass the linting checks.
• Ran python show_diff.py and posted the output as part of the PR.
• Modifications won't affect packages built in the future.

[conda-forge-webservices]

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 (recipe) and found it was in an excellent condition.

[psobolewskiPhD]

BTW i love the new yaml way of doing this! So much simpler and less intimidating! Kudos to y'all!

[hmaarrfk]

Patch difference:

noarch
noarch::npe2-0.7.4-pyhd8ed1ab_0.conda
noarch::npe2-0.7.3-pyhd8ed1ab_0.conda
-    "pydantic <2.0a0",
+    "pydantic",

[hmaarrfk]

BTW i love the new yaml way of doing this! So much simpler and less intimidating! Kudos to y'all!

this was all @beckermr

I now use Chatgpt and english to write these patches...

[psobolewskiPhD]

I now use Chatgpt and english to write these patches...

Wait, what? 🤯

Edit: sorry I didn't post the diff, I didn't realize that still applied. my bad.

[hmaarrfk]

Wait, what? 🤯

Yeha, i copy pasted the readme, and just told chatgpt to figure out how to fix my stuff. It might even be able to figure out the timestamp portion, but i still make that one manually!

[hmaarrfk]

Sorry, i'm just pretty excited about the removal of the pydantic v1 pin. That transition was painful on everybody i think...