Update pin for s2n

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update the pin for s2n. The current pinned version is 1.5.11, the latest available version is 1.5.13 and the max pin pattern is x.x.x. This migration will impact 3 feedstocks.

Checklist:

• The new version is a stable supported pin.
• I checked that the ABI changed from 1.5.11 to 1.5.13.

**Please note that if you close this PR we presume that the new pin has been rejected.

@conda-forge-admin please ping s2n

_{This PR was generated by https://github.com/regro/cf-scripts/actions/runs/13471345379 - please use this URL for debugging.}

[conda-forge-webservices]

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

I was asked to ping @conda-forge/s2n and so here I am doing that.

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

• ℹ️ top-level output has some malformed specs:

• In section test: python >= 3.8 Requirements spec fields should always be space-separated to avoid known issues in conda-build. For example, instead of name =version=build, use name version build`.

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