Update metrics to align with Prometheus best practices

[torredil]

What type of PR is this?

/kind cleanup

What is this PR about? / Why do we need it?

This PR updates the metrics registered by the node plugin to align with Prometheus best practices by:

• Adding a aws_ebs_csi namespace prefix.
• Following Prometheus conventions such as adding _total suffix for counter metrics.
• Using base units (seconds) instead of microseconds.

It also introduces a new parameter controller.deprecatedMetrics to disable registering the existing controller metrics that use an outdated namespace, such as:

cloudprovider_aws_api_request_duration_seconds_bucket{request="AttachVolume",le="0.005"} 0

Metrics using the new namespace will be registered by default if controller.enableMetrics is configured:

aws_ebs_csi_api_request_duration_seconds_bucket{request="AttachVolume",le="0.005"} 0

How was this change tested?

• make verify && make test
• Manually
• CI

Does this PR introduce a user-facing change?

BREAKING CHANGE: Node plugin metrics have been renamed to follow Prometheus best practices:
- Added "aws_ebs_csi_" prefix.
- Added "_total" suffix for counters.
- Changed time units from microseconds to seconds for all counters.

Controller plugin metrics now use the "aws_ebs_csi_" prefix instead of "cloudprovider_aws_".
Old metric names can be disabled via the controller.deprecatedMetrics parameter.

Note for reviewers:

Please note that time units have been changed from microseconds to seconds for all counters. The read/write IO latency histograms is observed in microseconds (the buckets for these histograms are retrieved directly from the log page which record the data in microseconds).

[github-actions]

Code Coverage Diff

File	Old Coverage	New Coverage	Delta
github.com/kubernetes-sigs/aws-ebs-csi-driver/pkg/cloud/handlers.go	6.5%	5.4%	-1.0

[torredil]

cc: @SuperQ

[ConnorJC3]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ConnorJC3

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

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

[ElijahQuinones]

/LGTM all metrics in seconds

[AndrewSirenko]

/lgtm