Apply rules_license to third_party tree

[aiuto]

See; license checking with Bazel for background.

We should use rules_license in Bazel. This would

• serve as a close-to-home testbed of the licensing rules
• be a more precise way of delineating what licenses are used in bazel itself and/or the build process.

Besides being of interest to the Bazel team, it is useful to anyone who distributes their own copy of Bazel, in either source or binary form.

The first round of actual work would be

• vendor rules_license into //third_party. It would be used for bulding Bazel but should not be re-exported as a tool
• create add a top level target to produce a licenses used audit for bazel
• go through third_party and add license definitions based on the actual license text

[aiuto]

This will also be useful for the debian packaging effort.

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[aiuto]

Most of third_party now has license rules. They need to have package_info rules too.