Rename "bzl visibility" to "load visibility" in comments and error messages
See discussion in review of unknown commit for rationale. It boils down to the fact that ".bzl visibility" would be the preferred formatting, but this is awkward to write at the beginning of sentences. Both "bzl" and "load" are pieces of terminology the user already knows. The only downside of "load" is that it can be interpreted as a verb rather than as part of a compound noun.
Changes:
- Generally, I substituted mentions of "bzl visibility" and "bzl-visibility" to be "load visibility".
- In some cases I just made it a bare "visibility" where it was obvious, in error messages created by a call to `visibility()`.
- In other cases I specify ".bzl load visibility" for extra clarity where context is weaker.
- One instance of "load-visibility" was de-hyphenated.
- Deleted mention in `visibility()`'s documentation that the feature is experimental.
Instances of "bzlVisibility" occur in the actual java symbols. I didn't change those because it's not user-visible, is extra churn for us, and can be misread more easily ("load" as a verb). I also didn't change the names of user-facing flags because renaming flags is an absolute nightmare and we don't have time before the Bazel cut anyway.
A follow-up will add more user concepts documentation for load visibility.
(This is probably the longest commit message I've written for such a trivial change.)
Work toward #11261.
PiperOrigin-RevId: 482897281
Change-Id: Iabb21e8b00b9cbb5335302e494bc0b0af0fa59af
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
