[ci:component:github.com/gardener/gardener-extension-provider-azure:v1.18.1->v1.19.1]

[gardener-robot-ci-2]

*Release Notes:

A bug is fixed which blocked the deletion of vmo based Azure cluster in case the vmo resource on Azure cannot be created.

Extension resources (`Infrastructure`, `ControlPlane`, etc.) are now deserialized in "strict" mode, including during validation by the validating webhook. This means that resources with fields that are not allowed by the API schema will be rejected by validation. Creating new shoots containing such resources will not be possible, and updating existing shoots will fail with an appropriate error until you manually update the shoot to make sure any extension resources contained in it are valid.

Azure: Improved NIC creation and deletion logic to handle NIC creation and deletions more gracefully.

provider-azure is now using a separate ManagedResource for ControlPlane CRDs that are installed in the Shoot cluster to separate the deletion of CRDs from the deletion of the RBAC for controller leader election.

`github.com/gardener/gardener` dependency is now updated to `v1.19.0`. For the complete list of changes, see the [release notes](https://github.com/gardener/gardener/releases/tag/v1.19.0).

`k8s.io/legacy-cloud-providers` is now updated to `v0.17.17`.

`k8s.io/legacy-cloud-providers` is now updated to `v0.18.17`.

`k8s.io/legacy-cloud-providers` is now updated to `v0.19.9`.

`k8s.io/legacy-cloud-providers` is now updated to `v0.20.5`.

The following terraform provider plugins are updated:
- hashicorp/terraform-provider-aws: 3.18.0 -> 3.32.0
- hashicorp/terraform-provider-google: 3.27.0 -> 3.59.0
- hashicorp/terraform-provider-google-beta: 3.27.0 -> 3.59.0

The cloud-controller-manager VPA does now specify minAllowed values to prevent too low resource recommendations from VPA that lead to OOM.

provider-azure does now specify minAllowed values by default for the extension controller to prevent too low recommendations from VPA that lead to OOMK.

All resources are now deleted from the shoot namespace during migration. Also, during restore the MCM is now scaled down to `0` and not deleted.

The Terraformer now instantly removes its finalizer from the state `ConfigMap` if the state is empty and `destroy` is called. A separate Terraform `destroy` is not executed.

Terraformer will now publish an additional image without any pre-installed terraform plugins.

Provides support for the Equinix Metal provider, which replaces the Packet one

The following images are updated (see [CHANGELOG](https://github.com/kubernetes-csi/external-snapshotter/blob/v2.1.4/CHANGELOG-2.1.md) for more details):
- quay.io/k8scsi/csi-snapshotter: v2.1.3 -> v2.1.4
- quay.io/k8scsi/snapshot-controller: v2.1.3 -> v2.1.4

A bug was fixed that caused terraform to leak its finalizer on ConfigMaps and Secrets in case of an interrupt during `terraform destroy`.

The terraformer-openstack use now the openstack provider in version v1.37.0

Curl has been removed from the Terraformer image.

The terraformer-openstack use now the openstack provider in version v1.36.0

A bug was fixed that caused terraform to leak its finalizer on ConfigMaps and Secrets in case of an interrupt during `terraform destroy`.

An issue causing Shoots to be marked as `Failed` (and no longer retried) on transient `not found` error is now fixed.

`k8s.io/legacy-cloud-providers` is now updated to `v0.20.2`.

The validator/admission component's Helm chart is now deploying a `VerticalPodAutoscaler` resource by default. If undesired or no VPA is available in the garden cluster then it can be turned of via `.Values.global.vpa.enabled=false`.

Azure admission controller now validates `CloudProfile` creation/update.

[gardener-robot]

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