[ci:component:github.com/gardener/gardener-extension-provider-gcp:v1.32.0->v1.33.1]

[gardener-robot-ci-1]

Release Notes:

Removed dead metrics code and refactored the remaining metrics code

updated image livenessprobe -> `v2.11.0`

Removes `node.machine.sapcloud.io/not-managed-by-mcm` annotation from nodes managed by the MCM.

`provider-gcp` extension now supports [Shoot Force Deletion](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_operations.md#force-deletion) for more details.). 

updated image gcp-compute-persistent-disk-csi-driver -> `v1.12.2`

updated image gcp-compute-persistent-disk-csi-driver -> `v1.11.1`

Force drain and delete volume attachments for nodes un-healthy due to `ReadOnlyFileSystem` and `NotReady` for too long

The following image is updated:
- registry.k8s.io/cloud-provider-gcp/gcp-compute-persistent-disk-csi-driver: v1.9.7 -> v1.9.9

New metrics introduced: 
- api_request_duration_seconds -> tracks time taken for successful invocation of provider APIs. This metric can be filtered by provider and service.
- driver_request_duration_seconds -> tracks total time taken to successfully complete driver method invocation. This metric can be filtered by provider and operation.
- driver_requests_failed_total -> records total number of failed driver API requests. This metric can be filtered by provider, operations and error_code.

Remove dependency to specific calico and cilium versions.

Added a new metric that will allow to get the number of stale (due to unhealthiness) machines  that are getting terminated

The following golang dependencies have been upgraded :
- `gardener/gardener`: `v1.81.0`->`v1.81.6`
- `k8s.io/*`: `v0.28.2`-> `v0.28.3`
- `sigs.k8s.io/controller-runtime`: `v0.16.2`-> `v0.16.3`

updated image snapshot-controller -> `v6.3.1`

MCM status code `ResourceExhausted` is now utilized in mcm-provider-gcp. Currently the `compute API` errors covered are:
- quota exceeded in zone
- insufficient resource in zone
- unavailable machinetype in zone

Makefile targets have changed: Introduced gardener-setup, gardener-restore, gardener-local-mcm-up, non-gardener-setup, non-gardener-restore,  non-gardener-local-mcm-up. Users can also directly use the scripts which are used by these makefile targets.

An issue causing nil pointer panic on scaleup of the machinedeployment along with trigger of rolling update, is fixed

updated image csi-resizer -> `v1.9.1`

Add readiness check for snapshot-validation-webhook

Added `errorCode` field in the `LastOperation` struct. This should be implemented only for the `CreateMachine` call in the `triggerCreationFlow`. This field will be utilized by Cluster autoscaler to do early backoff 

The provider-gcp extension does now support shoot clusters with Kubernetes version 1.28. You should consider the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.28.md) before upgrading to 1.28. 

`provider-gcp` no longer supports Shoots or Seeds with Кubernetes version < 1.24.

updated image csi-provisioner -> `v3.6.1`

The default `machine-safety-orphan-vms-period` has been reduced from 30m to 15m.

A new make target is introduced to add license headers.

updated image csi-attacher -> `v4.4.1`

Updated to go v1.20.5

Bump `k8s.io/*` deps to v0.27.2

The following golang dependencies have been upgraded :
- `gardener/gardener` to `v1.80.3`
- `k8s.io/*` to `v0.27.5`
- `sigs.k8s.io/controller-runtime` to `v0.16.2`

status.Status now captures underline cause, allowing consumers to introspect the error returned by the provider. WrapError() function could be used to wrap the provider error

Included `UnavailableReplicas` in determining if a machine deployment status update is needed

updated image registrar -> `v2.9.0`

An edge case where outdated DesiredReplicas annotation blocked a rolling update is fixed.

[gardener-robot]

@gardener-robot-ci-1 Thank you for your contribution.