Update dependency bazel_gazelle to v0.19.1

[renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
bazel_gazelle	http_archive	minor	0.18.2 -> v0.19.1

---

Release Notes

bazelbuild/bazel-gazelle

v0.19.1

Compare Source

Changes

• Rule names are now included in go_repository stderr output.
• Environment variables SSL_CERT_FILE and SSL_CERT_DIR are passed through to tools used by go_repository.
• The list of standard packages is correctly updated for Go 1.13.

v0.19.0

Compare Source

General changes

• The # gazelle:repository directive is now supported in WORKSPACE files. Gazelle will behave as if a repository rule were declared with the given kind and attributes. This may override other declared rules. This is useful for declaring rules that appear in other files and can't be managed with #gazelle:repository_macro. Thanks to @​blico.
• The update-repos command now accepts versions for each argument, for example, update-repos github.com/sirupsen/logrus@v1.4.0. For Go, the version suffixes follow the same format that go get accepts in module mode. Thanks to @​weixiao-huang.

Go changes

• go_repository has better support for visibility across submodules. For example, cloud.google.com/logging may now depend on internal packages in cloud.google.com, when both modules are unmodified go_repository rules. Previously, this required visibility attributes to be patched into the parent module.
• go_repository now handles WORKSPACE-based configuration more efficiently. A configuration file is derived from the relevant parts of WORKSPACE and any functions declared with # gazelle:repository_macro. go_repository rules are re-evaluated when the configuration file changes, not when WORKSPACE changes. Previously, non-Go-related changes to WORKSPACE would cause go_repository to be re-evaluated. Thanks to @​blico.
• go_repository now accepts a build_directives attribute, a list of directives to write into the root build file before running Gazelle. Thanks to @​linzhp.
• The # gazelle:go_visibility directive may be used to add labels to visibility attributes of Go rules. Thanks to @​linzhp.
• Generated .go files are no longer included in go_library srcs if they are consumed by another rule through the src or srcs attributes. Thanks to @​linzhp.

Proto changes

• Updated dependency resolution tables for know protos.

---

Renovate configuration

📅 Schedule: "at 7am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[k8s-ci-robot]

Hi @renovate-bot. Thanks for your PR.

I'm waiting for a bazelbuild member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nlopezgi]

/ok-to-test

[forking-renovate]

PR has been edited

👷 This PR has received other commits, so Renovate will stop updating it to avoid conflicts or other problems. If you wish to abandon your changes and have Renovate start over you may click the "rebase" checkbox in the PR body/description.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nlopezgi, renovate-bot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [nlopezgi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment