[cluster-autoscaler-release-1.27] allow customizing user agent for Azure cluster-autoscaler provider

[k8s-infra-cherrypick-robot]

This is an automated cherry-pick of #7033

/assign nojnhuh

The `AZURE_CLUSTER_AUTOSCALER_USER_AGENT_SUFFIX` variable can be used to customize the user agent for the Azure provider of cluster-autoscaler. Setting this to `-my-user-agent` results in a user agent like `Go/go1.22.5 (amd64-linux) go-autorest/v14.2.1 cluster-autoscaler-my-user-agent/v1.31.0-alpha.2`.

[k8s-ci-robot]

@k8s-infra-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-autoscaler-e2e-azure	2f9b861	link	false	/test pull-cluster-autoscaler-e2e-azure

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[Shubham82]

hold till CA 1.31 release

/hold

[comtalyst]

hold till CA 1.31 release

/hold

Why?

[Shubham82]

Hi @comtalyst, as per the following comment, we can cherry-pick the #7033 after CA 1.31 release.

@nojnhuh let's do that after the 1.31 release (which will include the necessary test files from main that landed in advance of the 1.31 release)

[nojnhuh]

@Shubham82 That comment about cherry-picking was related to a different set of changes. There shouldn't be anything hold this up from being merged before 1.31.

/hold cancel

[Shubham82]

Hi @nojnhuh, ok Maybe I missed something here, but I'm just wondering then why this pull-cluster-autoscaler-e2e-azure test case failed, as you mentioned in the following comment that the test case is not defined for corresponding release branches and we have to do some changes in test-infra. and then @jackfrancis mentioned that we can do that after 1.31. So I thought we would be going to backport those changes after CA 1.31.

[Bryce-Soghigian]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bryce-Soghigian, k8s-infra-cherrypick-robot

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/cloudprovider/azure/OWNERS [Bryce-Soghigian]

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

[Bryce-Soghigian]

I approved but most of these still wont get in without that azure e2e pipeline fix getting into these release branches