Update feedstock to use cirun-openstack-cpu-4xlarge with Cirun

[conda-forge-admin]

Note that only builds triggered by maintainers of the feedstock (and core)
who have accepted the terms of service and privacy policy will run
on Github actions via Cirun.

• Maintainers have accepted the terms of service and privacy policy
  at https://github.com/Quansight/open-gpu-server

[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/14930711187. Examine the logs at this URL for more detail.}

[apmorton]

ah, well, at least the linux builds are fast now. I should have read a little closer that mac/windows aren't supported.

[h-vetinari]

I should have read a little closer that mac/windows aren't supported.

There's a windows server sponsored by prefix.dev (used by the pytorch feedstock); perhaps the fine folks from prefix (@wolfv @baszalmstra etc.) would agree to let ray build on there as well (or anyscale covers part of the cost, or whatever agreement can be found).

For mac, we have some newly sponsored workers in the pipeline, but this hasn't been productionalized yet. You can try though if you're motivated (we'd need it for the tensorflow feedstock, but I haven't had time for this recently). CC @aktech

OTOH, given that the CI on mac/windows doesn't run into timeouts currently (as opposed to pytorch/tensorflow, where the only alternative would be to build manually), this is more of an optimization rather than essential.

[mattip]

CI (except for win-python3.10, which timed out) is passing. Anyone want to take a look? I restarted the single timed-out CI run