Parametrize the pydantic validation for better error message

[hmaarrfk]

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.

[jaimergp]

Is this slower by any chance? We should check. I remember seeing drastic performance improvements in constructor when we switched from pytest parametrization to an inner for loop. That had like thousands of cases, not lower hundreds like here, but just in case, I thought I'd ask.

[hmaarrfk]

Is this slower by any chance

this in my mind is the most worthwhile "test" that we can run and communicate to contributors.

I will check the logs and see if there is any appreciable difference:

This PR the parametrized tests take:
Start time: 2023-11-28T19:37:34.5421079Z
End time: 2023-11-28T19:37:34.5653805Z

under 1 second on 19 mins... i feel like we are ok