Adjust metric name due to upgrading the kube-state-metrics component

[istvanballok]

How to categorize this PR?

/area monitoring
/kind enhancement
/platform gcp

What this PR does / why we need it:

Adjust metric name due to upgrading the kube-state-metrics component

See gardener/gardener#6224

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

/cc @wyb1 @ialidzhikov

Release note:

Adjust metric name due to upgrading the kube-state-metrics component

This version of provider-gcp requires Gardener v1.51+. 

[kon-angelo]

/lgtm

[kon-angelo]

@istvanballok actually we need to wait the next gardener release containing the new kube-state-metrics version right ?

/hold

[wyb1]

/lgtm

[istvanballok]

@istvanballok actually we need to wait the next gardener release containing the new kube-state-metrics version right?

Yes. Once (probably soon) the PR gardener/gardener#6224 is merged and the next gardener version is released, a new version of the extension could also be released.

If the extension is released earlier, the dashboard wouldn't show the requests and limits but it is still possible to query the corresponding information by manually adjusting the dashboards or executing those queries.

If gardener is released earlier, there is a temporary recording rule which stores the new metrics under the old names to prevent breaking the dashboards.

[istvanballok]

actually we need to wait the next gardener release containing the new kube-state-metrics version right ?

See gardener/gardener-extension-provider-alicloud#506 (comment):
now that gardener v1.51.0 has been released, the adjustments in (all) the extensions could also be released.

[dkistner]

/lgtm