Node Tasks Node 24 upgrade

[rajmishra1997]

Context

Describe the context or motivation for this PR. Include links to any related Azure DevOps Work Items or GitHub issues.
📌 How to link to ADO Work Items
Node 24 migration for Node sub-group Tasks

1. useNode AB#2340639
2. NodeTool AB#2340638

---

Task Name

Name of the updated or newly created pipeline task.

1. useNode
2. NodeTool

---

Description

Summarize the changes made in this PR clearly and concisely.
task version is bumped, Node 24 added in execution and task-lib version is bumped

Risk Assessment (Low / Medium / High)

Assess the level of risk and provide reasoning (e.g., scope, impact, backward compatibility).
Low

Change Behind Feature Flag (Yes / No)

Can this change be behine feature flag, if not why?
No code changes

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.
  Design Document

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.
  No

---

Unit Tests Added or Updated (Yes / No)

Indicate whether unit tests were added or modified to reflect these changes.
No

Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).
  No

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.
  No

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.
  No

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

---

Checklist

• Related issue linked (if applicable)
• Task version was bumped — see versioning guide
• Verified the task behaves as expected

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[sanjuyadav24]

canary-test are failing for this

[rajmishra1997]

canary-test are failing for this

Canary test changes are required for this, fix PR: https://github.com/microsoft/azure-pipelines-canary/pull/1318

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[rajmishra1997]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[tarunramsinghani]

@rajmishra1997 , can you please add the links to successful test pipelines for this....