Update pin for pytorch

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update the pin for pytorch. The current pinned version is 1.13, the latest available version is 2.0 and the max pin pattern is x.x. This migration will impact 25 feedstocks.

Checklist:

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

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

@conda-forge-admin please ping pytorch-cpu
This PR was generated by https://github.com/regro/cf-scripts/actions/runs/4612719562, 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/pytorch-cpu and so here I am doing that.

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

[hmaarrfk]

@Tobias-Fischer do you want this before the torvision update?

[Tobias-Fischer]

Let's wait a little till we have figured out the triton stuff?

[h-vetinari]

@Tobias-Fischer do you want this before the torvision update?

torchvision is running into issues regardless... conda-forge/torchvision-feedstock#71

Though those aren't a huge deal and can be worked around in other ways, so I'm not proposing to hurry. Still...

Let's wait a little till we have figured out the triton stuff?

IIUC, triton is not essential for the operation of pytorch? Can we uncouple the 2.0 migration from improving the triton-integration?

[Tobias-Fischer]

Sure fine with me

[hmaarrfk]

ok lets see what happens.