Make maxNodeStartupTime configurable

[lxuan94-pp]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR introduces a new configurable flag --max-node-startup-time to the Cluster Autoscaler, which is currently hard-coded to 15 minutes in clusterstate.go. Similar to the existing --max-node-provision-time flag, this allows users to configure the maximum time the autoscaler should wait for a node to transition from registered to ready, providing more flexibility in environments where node readiness may vary due to image size, initialization scripts, or network conditions.

Which issue(s) this PR fixes:

NA

Special notes for your reviewer:

• The new flag is consistent with existing time-based configuration flags.
• Default behavior remains unchanged unless the new flag is set(fallback to 15mins hard-coded value if not set).
• Helps operators tune autoscaler behavior for different environments
• This feature has been tested on an OCI provider cluster

Does this PR introduce a user-facing change?

Yes
If yes, a release note is required:
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".

For more information on release notes see: https://git.k8s.io/community/contributors/guide/release-notes.md
-->

Cluster Autoscaler now supports a new flag `--max-node-startup-time` to configure the maximum wait time for a node to become ready. 

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: lxuan94-pp / name: Xuan Liu (189d25b, 312756a)

[k8s-ci-robot]

Welcome @lxuan94-pp!

It looks like this is your first PR to kubernetes/autoscaler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/autoscaler has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @lxuan94-pp. Thanks for your PR.

I'm waiting for a kubernetes 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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lxuan94-pp
Once this PR has been reviewed and has the lgtm label, please assign aleksandra-malinowska for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• cluster-autoscaler/OWNERS

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