chore(all): auto-regenerate .pb.go files (#957)

This is an auto-generated regeneration of the .pb.go files by
cloud.google.com/go/internal/gapicgen. Once this PR is submitted, genbot will
update the corresponding PR to depend on the newer version of go-genproto, and
assign reviewers. Whilst this or any regen PR is open in go-genproto, genbot
will not create any more regeneration PRs. If all regen PRs are closed,
gapicgen will create a new set of regeneration PRs once per night.

If you have been assigned to review this PR, please:

- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship. That will prompt
genbot to assign reviewers to the google-cloud-go PR.

Corresponding google-cloud-go PR: googleapis/google-cloud-go#7208

Changes:

docs(notebooks): Minor formatting fixes to reference documentation
  PiperOrigin-RevId: 499362676
  Source-Link: googleapis/googleapis@870a5ed

chore(gsuiteaddons): Configure Ruby client library generation for gsuiteaddons
  PiperOrigin-RevId: 499356666
  Source-Link: googleapis/googleapis@c3845dd

feat(batch): support secret and encrypted environment variables in v1
  PiperOrigin-RevId: 499338464
  Source-Link: googleapis/googleapis@af050dc

chore(ruby): Configure client for google-cloud-bigquery-data_policies-v1
  PiperOrigin-RevId: 499326312
  Source-Link: googleapis/googleapis@882eada

feat(bigquery/datatransfer): Add location methods
  PiperOrigin-RevId: 499272288
  Source-Link: googleapis/googleapis@62c5867

chore: regenerate API index

  Source-Link: googleapis/googleapis@025f73e

feat(artifactregistry): Add location methods
  PiperOrigin-RevId: 499263614
  Source-Link: googleapis/googleapis@ba2db0d

chore: regenerate API index

  Source-Link: googleapis/googleapis@1a54b1f

feat: add a DataLineage API
  PiperOrigin-RevId: 498346995
  Source-Link: googleapis/googleapis@7977517

refactor: Copy SourcePosition message from v1alpha/syntax.proto to conformance_service.proto
  PiperOrigin-RevId: 498255774
  Source-Link: googleapis/googleapis@e6a9ae2

feat(container): add etags for cluster and node pool update operations
  Clients may now optionally specify the previously read etag for a cluster or node pool during update requests. The etag is regenerated every time the object is updated. If an etag is provided, it will be checked against the current etag, and the request will be rejected on mismatch. This is particularly useful for allowing two clients to concurrently update a repeated field without overwriting each other.

  PiperOrigin-RevId: 498249600
  Source-Link: googleapis/googleapis@9a294bf