Transfer tools_remote to bazel-contrib

[meteorcloudy]

Description:

This issue proposes transferring the tools_remote repository from the bazelbuild GitHub organization to the bazel-contrib GitHub organization, which is owned by the Community for Bazel project under the Linux Foundation.

GitHub Discussion: https://github.com/orgs/bazelbuild/discussions/2

Impacts:

• GitHub issues & PRs will be transferred to the new repository.
• Branch protection rules will need to be transferred to the new repository.
• Individual maintainers will be transferred to the new repository.
• GitHub teams will NOT be transferred to the new repository and will need to be re-created.
• Bazel CI configurations will need to be updated to point to the new repository.

Read more on Transferring a repository from GitHub documentation.

Checklist:

• Obtain approval from the current project maintainers (@werkt).
• Obtain approval from the bazel-contrib SIG (@alexeagle).
• Initiate the transfer process on GitHub (@meteorcloudy).
• Update Bazel CI settings and confirm presubmit & postsubmit work (@meteorcloudy).

[alexeagle]

SIG meeting: decided not to include this one in the bulk-approve bulk-transfer.
Reasoning:
No MODULE file, only one recent maintainer, no changes in the last year, no releases.

We can still consider moving it to bazel-contrib org but it would be a standalone effort, not approving today.

[meteorcloudy]

@werkt Is this repo essentially in maintenance mode?

[werkt]

Yes. This is updated as the remote execution api changes and is (to my knowledge) the only tool capable of reading the output of --remote_grpc_log in bazel.

[alexeagle]

Can this move along with buildfarm/buildfarm#1847 ?

[werkt]

It can see the same resolution as that transfer, yes. There's no need for further action here.

[alexeagle]

FYI if you need any policy bits to facilitate the transfer from github.com/bazelbuild I'm happy to help with a temporary stop through github.com/bazel-contrib and then on to wherever you have in mind @werkt