Add opentelemetry tracing on gRPC calls for self-managed drivers

[Fricounet]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test

/kind feature

/kind flake

What this PR does / why we need it:
Allow self-managed drivers to add basic tracing on the gRPC calls received by the driver (controller and node) using opentelemetry. This is useful to help monitor and debug driver issues on top of existing logs.
Otel tracing can be enabled using the flag --enable-otel-tracing. Defaults to false.

Which issue(s) this PR fixes:
Fixes #1299

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Added enable-otel-tracing flag to enable opentelemetry tracing for self-managed drivers. The flag is disabled by default

[k8s-ci-robot]

Welcome @Fricounet!

It looks like this is your first PR to kubernetes-sigs/gcp-compute-persistent-disk-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/gcp-compute-persistent-disk-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Fricounet. 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.

[Fricounet]

cc @mattcary, I finally got the time to submit the PR

[Fricounet]

@mattcary could you take a look at this PR? 🙏

[mattcary]

Sorry for the delay in looking at this, we got backed up behind some issues. I'll take a look.

[mattcary]

/lgtm
/approve

I'll probably need to re-lgtm after you resolve the merge conflict.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

[Fricounet]

thanks for your review, I just rebased the PR :)

[mattcary]

/lgtm