Add notes about BoundingBoxes transform utils in ops/boxes docstrings

[bmmtstb]

Added documentation to multiple functions in torchvision.ops.boxes as proposed by #8190 .

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ You can merge normally! (9 Unrelated Failures)

As of commit f100194 with merge base 71b27a0 ():

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• CMake / macos (macos-12) / macos-job (gh)
  The process '/usr/local/bin/git' failed with exit code 128
• CMake / windows (windows.4xlarge, cpu) / windows-job (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 128
• Tests / unittests-macos (3.10, macos-12) / macos-job (gh)
  The process '/usr/local/bin/git' failed with exit code 128
• Tests / unittests-macos (3.11, macos-12) / macos-job (gh)
  The process '/usr/local/bin/git' failed with exit code 128
• Tests / unittests-macos (3.9, macos-12) / macos-job (gh)
  The process '/usr/local/bin/git' failed with exit code 128
• Tests / unittests-windows (3.10, windows.4xlarge, cpu) / windows-job (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 128
• Tests / unittests-windows (3.11, windows.4xlarge, cpu) / windows-job (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 128
• Tests / unittests-windows (3.8, windows.4xlarge, cpu) / windows-job (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 128
• Tests / unittests-windows (3.9, windows.4xlarge, cpu) / windows-job (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 128

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

[facebook-github-bot]

Hi @bmmtstb!

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 a lot for the PR @bmmtstb ! It looks great, I just made some minor comments below regarding formatting. LMK what you think

[bmmtstb]

I implemented the requested changes.

[NicolasHug]

Thanks a lot @bmmtstb !!