Update torch requirement from ~=1.9.1 to ~=1.10.1

[dependabot]

Updates the requirements on torch to permit the latest version.

Release notes

Sourced from torch's releases.

PyTorch 1.10.1 Release, small bug fix release

This release is meant to fix the following issues (regressions / silent correctness):

• torch.nn.cross_entropy silently incorrect in PyTorch 1.10 on CUDA on non-contiguous inputs #67167
• channels_last significantly degrades accuracy #67239
• Potential strict aliasing rule violation in bitwise_binary_op (on ARM/NEON) #66119
• torch.get_autocast_cpu_dtype() returns a new dtype #65786
• Conv2d grad bias gets wrong value for bfloat16 case #68048

The release tracker should contain all relevant pull requests related to this release as well as links to related issues

Changelog

Sourced from torch's changelog.

Releasing PyTorch

• General Overview
• Cutting release branches
  • Making release branch specific changes
  • Getting CI signal on release branches:
• Drafting RCs (https://github.com/pytorch/pytorch/blob/master/Release Candidates)
  • Release Candidate Storage
  • Cherry Picking Fixes
• Promoting RCs to Stable
• Special Topics
  • Updating submodules for a release

General Overview

Releasing a new version of PyTorch generally entails 3 major steps:

1. Cutting a release branch and making release branch specific changes
2. Drafting RCs (Release Candidates), and merging cherry picks
3. Promoting RCs to stable

Cutting release branches

Release branches are typically cut from the branch viable/strict as to ensure that tests are passing on the release branch.

Release branches should be prefixed like so:

release/{MAJOR}.{MINOR}

An example of this would look like:

release/1.8

Please make sure to create branch that pins divergent point of release branch from the main branch, i.e. orig/release/{MAJOR}.{MINOR}

Making release branch specific changes

These are examples of changes that should be made to release branches so that CI / tooling can function normally on them:

• Update target determinator to use release branch:
  • Example: pytorch/pytorch#40712
• Update backwards compatibility tests to use RC binaries instead of nightlies
  • Example: pytorch/pytorch#40706
• A release branches should also be created in pytorch/xla and pytorch/builder repos and pinned in pytorch/pytorch

... (truncated)

Commits

• 302ee7b [release/1.10] Fix adaptive_max_pool2d for channels-last on CUDA (#67697) (#6...
• 0c91a70 [release/1.10] TST Adds test for non-contiguous tensors (#64954) (#69617)
• eadb038 [ONNX] Update onnxruntime to 1.9 for CI (#65029) (#67269) (#69641)
• 8416d63 Fix strict aliasing rule violation in bitwise_binary_op (#66194) (#69619)
• c78cead [LiteInterpreter] Specify Loader to yaml.load (#67694) (#69642)
• 70af72c Fix python version in test tools CI job (#66947) (#69643)
• 36449ea (torch/elastic) add fqdn hostname to error printout (#66182) (#66662)
• b544cbd Handle shared memory cases in MathBitFallback (#66667)
• ddf3092 Disable .numpy() and .tolist() for tensor subclasses subclasses and f… (#66642)
• cc360fa Delete extraneous whitespaces
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #120.