Updated `grpc` to 1.62.0, `protobuf` to 25.3, and `abseil-cpp` to 20240116.0 to fix CVE-2023-44487.

[PawelWMS]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• [X] The toolchain has been rebuilt successfully (or no changes were made to it)
• [X] The toolchain/worker package manifests are up-to-date
• [X] Any updated packages successfully build (or no packages were changed)
• [X] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• [X] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• [X] All package sources are available
• [X] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• [X] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• [X] All source files have up-to-date hashes in the *.signatures.json files
• [X] sudo make go-tidy-all and sudo make go-test-coverage pass
• [X] Documentation has been updated to match any changes to the build system
• [X] Ready to merge

---

Summary

Updated grpc to version 1.62.0 to fix CVE-2023-44487. This also required updating protobuf and abseil-cpp. Unfortunately, our current version of grpc is too far behind for it to be possible to backport a patch.

Does this affect the toolchain?

No.

Associated issues

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2023-44487

Test Methodology

• Local builds with tests.
• PR check.
• Full build.