Update version to v1.5.0

[flferretti]

It's still not clear to me why #39 is failing, even by looking at the logs. In the meanwhile, this is a manual version update.

Closes #38
Closes #39

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

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

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12667752978. Examine the logs at this URL for more detail.}

[flferretti]

The problem related to OSX and Windows build on lief seems to be solved (probably just rerendering was necessary). Yet, I'm still getting an error on "libcrypt":

/home/conda/.cache/packman/python/3.10.5-1-linux-x86_64/python: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
/home/conda/.cache/packman/python/3.10.5-1-linux-x86_64/python: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory