Fix 8 ClangTidyLegacy findings:
* inclusion of forwarding header 'thread/thread.h'; use 'third_party/gloop/thread/thread.h' instead. For more info, see go/clang_tidy/checks/google3-legacy-forwarding-headers (3 times)
* inclusion of forwarding header 'thread/thread_options.h'; use 'third_party/gloop/thread/thread_options.h' instead. For more info, see go/clang_tidy/checks/google3-legacy-forwarding-headers (3 times)
* inclusion of forwarding header 'net/grpc/public/include/grpcpp/support/time_google.h'; use 'third_party/grpc/include/grpcpp/support/time.h' instead. For more info, see go/clang_tidy/checks/google3-legacy-forwarding-headers
* inclusion of forwarding header 'thread/fiber/fiber.h'; use 'third_party/gloop/thread/fiber/fiber.h' instead. For more info, see go/clang_tidy/checks/google3-legacy-forwarding-headers

This CL looks good? Just grant approval!
This CL doesn’t look good? This is what you can do:
* Revert this CL, by replying "REVERT: <provide reason>"
* File a bug under go/clang-tidy-bug for category ClangTidyLegacy if there's an issue with the CL content.
* File a bug under go/rosie-bug if there's an issue with how the CL was managed.
* For all other issues such as the formatting of the CL, please file a bug under
go/clrobot-bug.
* Revert this CL and not get a CL that cleans up these paths in the future by
replying "BLOCKLIST: <provide reason>". This is not reversible! We recommend to
opt out the respective paths in your CL Robot configuration instead:
go/clrobot-opt-out.

This CL was generated by CL Robot - a tool that cleans up code findings
(go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/METADATA by
following go/clrobot#how-to-opt-in. Anything wrong with the signup? File a bug
at go/clrobot-bug.

#clrobot #google3-legacy-forwarding-headers

BEGIN_PUBLIC
Automated Code Change
END_PUBLIC

Tested:
    Local presubmit tests passed.
PiperOrigin-RevId: 998524108
Change-Id: I67cf807b38214c9eb77649477a2628964f98fabe