Rebuild for fmt 11 and skip Windows' builds

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update fmt11.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/10580425710 - please use this URL for debugging.}

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

[jjerphan]

@conda-forge-admin, please rerender

[jjerphan]

@h-vetinari: I am proposing to skip the Windows' builds via 6b1187f (I can give more arguments if needed).

[h-vetinari]

I think I saw you mention somewhere that windows isn't really supported by upstream folly anyway? I don't know the project well, so IMO fine to do that if that's what it takes.

I also checked mamba repoquery whoneeds -c conda-forge -p win-64 folly, and it seems that there are zero other packages depending on this on windows 🥳

[jjerphan]

I think I saw you mention somewhere that windows isn't really supported by upstream folly anyway? I don't know the project well, so IMO fine to do that if that's what it takes.

Yes, 6b1187f's commit message gives a few pointers (for instances see the build notes of folly, and facebook/folly#962 as one of several issues mentioning the non-official support of Windows).

I also checked mamba repoquery whoneeds -c conda-forge -p win-64 folly, and it seems that there are zero other packages depending on this on windows 🥳

Thanks! 🙏

Some packages depending on folly might be distributed for Windows as python wheels on PyPI but might fails to be distributed on conda-forge (this is the case of ArcticDB which has had problem with the unsane build of folly, see man-group/ArcticDB#449).

---

On a side-note, I guess we could also stop distributing new versions of folly on conda-forge due to the nature of the project (which have to pin it to a given version to have consistent state). See #185 for more context.

Anyway, if everything is good for you, I let you approve and merge this PR.

[h-vetinari]

Anyway, if everything is good for you, I let you approve and merge this PR.

You are the maintainer here, not me. 😉

You have my LGTM!

[jjerphan]

Moving on with the decision to remove Windows builds, given the discussed elements in this thread and assuming future requests if any.