Transfer vscode-bazel to bazel-contrib

[meteorcloudy]

Description:

This issue proposes transferring the vscode-bazel 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 (@fweikert, @jfirebaugh, @cameron-martin).
• 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]

Notes from SIG meeting: this transfer was unanimously approved by a thumbs-up vote.

[vogelsgesang]

Obtain approval from the current project maintainers (@fweikert, @jfirebaugh, @cameron-martin).

Approved

After transferring the repository itself, we should probably also figure out what we want to do about the ownership of the MarketPlace extension

[meteorcloudy]

@fweikert I think we discussed this before, could we transfer the extension to a different account?

[vogelsgesang]

Yep, there was some discussion around this previously in Slack in this thread

[meteorcloudy]

Cool, then I guess we can continue to help publishing the extension for now. I'll do the transfer now

[meteorcloudy]

Done, please check CI/CD works correctly.