Constrain QCSubmit against QCElemental Pydantic v2 migration

[mattwthompson]

This is yet another case of constraining 0.x upstreams against changes propagating out from the Pydantic v2 breaks

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.

$ python recipe/show_diff.py --subdirs noarch       15:30:00  ☁  qcsubmit-qcelemental-pydantic-migration ☀ 𝝙
================================================================================
================================================================================
noarch

[conda-forge-admin]

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/meta.yaml) and found it was in an excellent condition.

[xhochy]

The diff in CI is not showing any changes.

[mattwthompson]

Hmm thanks ... will have a closer look

[mattwthompson]

The script to locally diff things isn't working as expected; I've tried a few dozen combinations of inputs and everything, including things like below with nearly no restrictions, and everything shows an empty diff locally. This bit in the README leads me to believe it's not really meant to be trusted, so I'll be firing off some stuff to CI to see what works

if:
  name: openff-qcsubmit
  timestamp_lt: 1728401565
  version_le: 0.53
then:
  - add_depends: espaloma

[mattwthompson]

Not sure what I'm doing wrong here

• I'm basing my changes off of something that worked previously (and not so long ago) https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/806/files
• Where in the CI logs would the diff be?