limit grpc logging info to a configurable character limit

[leiyiz]

What type of PR is this?
/kind bug

What this PR does / why we need it:
ListVolume call generates tons of log items because by default the entirety of the grpc response body gets logged out. That consumes log space really fast and we want to limit how much can be logged in the same message.

This might impact some visibility into what's going on with ListVolume call.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

didn't find obvious way to make the log limit configurable. Pls advise of otherwise

Does this PR introduce a user-facing change?:

Logging for gRPC call is now limited to 10000 char by default, and configurable with flag --grpc-log-char-cap

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leiyiz

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

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

[amacaskill]

/retest

[amacaskill]

lgtm but just looks like you need to change the tests that call gceDriver.Run(endpoint) --> gceDriver.Run(endpoint, grpcLogCharCap)

[leiyiz]

/test pull-gcp-compute-persistent-disk-csi-driver-sanity

[leiyiz]

fixed test failure, @amacaskill ptal

[judemars]

Hey there! Just letting you know that I have just fixed and re-enabled the sanity tests for PD in go/pdcsi-oss-driver/issues/990 so if you experience failures in your sanity test PR gate build because you're on an old branch before the tests were fixed, merging the latest commits from master into this branch it should make them pass. Let me know if you have any questions!

[amacaskill]

/lgtm