Update third_party dependencies

[alexreinking]

Newer versions of CMake (>=4.0) have dropped backwards compatibility with older versions of CMake (<3.5). All of double-conversion, sentencepiece, and utf8proc point to commits that declare minimum CMake versions older than that, breaking the build. Fortunately, the minimum CMake versions have all been bumped upstream, and just updating the submodules seems to work.

Fixes #2294

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/text/2295

• 📄 Preview Python docs built from this PR

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

❌ 9 New Failures, 3 Cancelled Jobs, 3 Unrelated Failures

As of commit 28ccf3c with merge base bde7ecd ():

NEW FAILURES - The following jobs have failed:

• Bandit / build (gh)
  Process completed with exit code 1.
• Build documentation / build / Build doc (gh)
  RuntimeError: Command docker exec -t f951e3dc97c020e31b4f3149071dc77ae4dd99c63db07c11edcec23d72d37dfe /exec failed with exit code 1
• CodeQL / build (gh)
  Encountered an error while trying to determine feature enablement: HttpError: Resource not accessible by integration
• Integration Test / tests (3.8) / linux-job (gh)
  RuntimeError: Command docker exec -t 05f7f036ecb60589b6d4fcb0a1aa4e92a504ff21b8f776c8f6c5561a67201c9a /exec failed with exit code 1
• Lint / python-source-and-configs / linux-job (gh)
  RuntimeError: Command docker exec -t 650d8014df93ebf2b30f4830b4f240465545a8cc05e8d30ca2d75eb943070da4 /exec failed with exit code 1
• Unit-tests on Linux CPU / tests (3.10) / linux-job (gh)
  RuntimeError: Command docker exec -t 48e6ab85b8869410a9aaf62a48706a56318044d74fa9443ae688a55ac1e968be /exec failed with exit code 1
• Unit-tests on Linux CPU / tests (3.8) / linux-job (gh)
  RuntimeError: Command docker exec -t 1601505720a05c026f3b61d060788d5645ea697cdc5ef17f57e4742f676d4db1 /exec failed with exit code 1
• Unit-tests on Linux CPU / tests (3.9) / linux-job (gh)
  RuntimeError: Command docker exec -t c04bf87494bc4a930964640d3e823a74b074137b8e3da34b11ad35f101ef52d2 /exec failed with exit code 1
• Unit-tests on Linux GPU / tests (3.8, 11.7) / linux-job (gh)
  RuntimeError: Command docker exec -t 8da5f997757dc6f06eb47e7bd2ab80e39dab91bca27ab82f703c38bf263b86d0 /exec failed with exit code 1

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• Unit-tests on Macos CPU / tests (3.10) / macos-job (gh)
• Unit-tests on Macos CPU / tests (3.8) / macos-job (gh)
• Unit-tests on Macos CPU / tests (3.9) / macos-job (gh)

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• Unit-tests on Windows CPU / tests (3.8) / windows-job (gh) (matched win rule in flaky-rules.json)
  ##[error]The operation was canceled.

BROKEN TRUNK - The following jobs failed but was present on the merge base:

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

• Unit-tests on Windows CPU / tests (3.10) / windows-job (gh) (trunk failure)
  ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject
• Unit-tests on Windows CPU / tests (3.9) / windows-job (gh) (trunk failure)
  ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

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

[facebook-github-bot]

Hi @alexreinking!

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 [email protected]. Thanks!