fix: pin back lief even more for conda-build

[beckermr]

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.

There is still an open conda-build issue for lief 0.15, so pin back even more.

xref: conda/conda-build#5627

[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.

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• github-actions: passed

Thus the PR was passing and merged! Have a great day!

[maresb]

@beckermr, this doesn't fix it yet, since py-lief 0.16.2 is in quay.io/condaforge/linux-anvil-x86_64:alma9:

docker run --rm -it quay.io/condaforge/linux-anvil-x86_64:alma9 micromamba list py-lief
List of packages in environment: "/opt/conda"

  Name     Version  Build            Channel    
──────────────────────────────────────────────────
  py-lief  0.16.2   py312h2ec8cdc_0  conda-forge

The command in the runner:

micromamba install --root-prefix /home/conda/.conda --prefix /opt/conda --yes --override-channels --channel conda-forge --strict-channel-priority pip python=3.12 conda-build conda-forge-ci-setup=4 'conda-build>=24.1'

doesn't pick up the new repodata patch.

See for example conda-forge/mkl-service-feedstock#38

[beckermr]

Ouch. We'll need to rebuild the docker images. I am away from my keyboard, so feel free to go ahead and submit a pr. Otherwise I can do it later.