chore: rework cluster-autoscaler Scaleway cloudprovider integration

[pablo-ruth]

What type of PR is this?

/kind feat

What this PR does / why we need it:

This PR reworks the Scaleway provider integration. We've updated the autoscaler's API calls to deprecate legacy infrastructure components and improve scaling performance. The new implementation optimizes our backend handlers, resulting in faster response times and more efficient cluster scaling operations.

Scaleway cloudprovider optimization

[k8s-ci-robot]

@pablo-ruth: The label(s) kind/feat cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?

/kind feat

What this PR does / why we need it:

This PR reworks the Scaleway provider integration. We've updated the autoscaler's API calls to deprecate legacy infrastructure components and improve scaling performance. The new implementation optimizes our backend handlers, resulting in faster response times and more efficient cluster scaling operations.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pablo-ruth / name: Pablo RUTH (543e339, 62dd8bc)

[k8s-ci-robot]

Hi @pablo-ruth. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jackfrancis]

/ok-to-test
/release-note-edit

Scaleway cloudprovider optimization

[jackfrancis]

/assign @louisportay

[k8s-ci-robot]

@jackfrancis: GitHub didn't allow me to assign the following users: louisportay.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @louisportay

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jackfrancis]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jackfrancis, louisportay, pablo-ruth

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:

• cluster-autoscaler/OWNERS [jackfrancis]

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

[jackfrancis]

@pablo-ruth @louisportay do you build CA bits for Scaleway customers based on the upstream release branches for particular versions of Kubernetes or do you re-use the upstream images? Happy to backport these updates across the 1.31+ branches if that helps.

[louisportay]

We plan to reuse upstream images and sync release branches starting from 1.34.
So you don't have to worry about backporting (though it's nice asking :) )