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

[gardener-robot-ci-1]

Release Notes:

updated image azure-cloud-controller-manager -> `v1.27.10`

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

A new make target is introduced to add license headers.

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.

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

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

updated image csi-registrar -> `v2.9.0`

Always set the `vmType` in cloud-provider configuration files.

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

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

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

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

Fix failing validation  when overlay config is empty.

updated image azure-cloud-controller-manager -> `v1.26.16`

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

updated image azure-cloud-controller-manager -> `v1.25.20`

The provider-azure 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. 

VM types with azure accelerated networking now work out-of-the-box with calico's ebpf dataplane.

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

Updated quota exceeded error labeling 

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

updated image azure-cloud-node-manager -> `v1.27.10`

Remove dependency to specific calico and cilium versions.

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.

updated image azure-cloud-node-manager -> `v1.25.20`

Updated to go v1.20.5

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

updated image azure-cloud-node-manager -> `v1.28.2`

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

Add readiness check for snapshot validation webhook

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`

Update `k8s.io/client-go` from `v0.26.3` to `v0.26.4` to resolve panic on health-checking special shoots.

updated image azure-cloud-node-manager -> `v1.26.16`

updated image livenessprobe -> `v2.11.0`

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 

Removed dead metrics code and refactored the remaining metrics code

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

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

updated image azure-cloud-controller-manager -> `v1.28.2`

Bastion instances now use the latest ubuntu server 22.04 LTS version 

[gardener-robot]

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