Bump build number and rebuild against latest libavif on Windows

[traversaro]

See conda-forge/libavif-feedstock#32 (comment) and conda-forge/libavif-feedstock#33 .

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

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

I do have some suggestions for making it better though...

For recipe:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[traversaro]

@conda-forge-admin, please rerender

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

[github-actions]

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

I tried to rerender for you but ran into some issues. Please check the output logs of the latest webservices GitHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or you can try rerendeing locally.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/libheif-feedstock/actions/runs/9287782600.

[traversaro]

@conda-forge-admin, please rerender

[hmaarrfk]

Given the last few migrations haven't taken place I'm going to jump in here since I know it is blocking @traversaro

@frmdstryr is there a particular reason why the migrations haven't been merged?
If it is just you didn't have time that is fine, we can have other co-maintainers jump in when they need to.

If you have compatibility concerns it would be great to learn about them so we can address them.