Sanitize GRPC logging

[tsmetana]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
We should use the protosanitizer on the GRPC logs in order not to leak some sensitive data to the logs.

Special notes for your reviewer:
This PR adds dependency on protosanitizer from csi-lib-utils, hence the changes in vendor, go.mod, go.sum, etc.

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @tsmetana. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[jsafrane]

/ok-to-test

[mattcary]

/lgtm
/approve
/retest

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mattcary, tsmetana

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 [mattcary]

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

[msau42]

We originally added protosanitizer and removed it because we found it had signficant performance degradation. Our driver does not use secrets so I don't think we need it. #356 (comment)