Add roi_align nondeterministic support for XPU

[frost-intel]

Fixes part of intel/torch-xpu-ops#1264, along with pytorch/pytorch#147541, to allow XPU device to use the non-deterministic compiled _roi_align op.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/8931

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 4 New Failures, 4 Pending, 1 Unrelated Failure

As of commit 79da54b with merge base d462da2 ():

NEW FAILURES - The following jobs have failed:

• Tests / unittests-linux (3.10, linux.12xlarge, cpu) / linux-job (gh)
  RuntimeError: Command docker exec -t d162a150de4393054bce8262d11ee3eab83c4dd394178372f4b4e89cd8f19947 /exec failed with exit code 1
• Tests / unittests-linux (3.11, linux.12xlarge, cpu) / linux-job (gh)
  RuntimeError: Command docker exec -t 00262f93d9f8913fa47997a33cc18928833451895560b987de5ff736a4aa127c /exec failed with exit code 1
• Tests / unittests-linux (3.12, linux.12xlarge, cpu) / linux-job (gh)
  RuntimeError: Command docker exec -t c5a5c160b52e9a413f3f06983c6cc43f9f8c5b18de680139d8d0aff2b346dd95 /exec failed with exit code 1
• Tests / unittests-linux (3.9, linux.12xlarge, cpu) / linux-job (gh)
  RuntimeError: Command docker exec -t c6fab3b98dac17cc0a94eb1124f8017c7aa32672f40db45b42ab5fac1d7426f7 /exec failed with exit code 1

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• Tests / unittests-windows (3.9, windows.g5.4xlarge.nvidia.gpu, cuda, 11.8) / windows-job (gh) (trunk failure)
  AttributeError: '_OpNamespace' 'image' object has no attribute '_jpeg_version'

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

Hi @frost-intel!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[NicolasHug]

Thanks @frost-intel