FileSystem 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

AB#2340620
AB#2340619

Task Name

Name of the updated or newly created pipeline task.

1. FtpUploadV2
2. InstallSSHKeyV0

---

Description

Summarize the changes made in this PR clearly and concisely.

Task built using BuildConfigGen uisng Node24_overwrite config

---

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, no code change

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.).

Task: InstallSSHKey runs as Pre-Job
Tested in DevFabric, after enabling knob for agent UseNode24/AGENT_USE_NODE24
Pipeline used:
`
trigger: none

pool:
name: Default

jobs:

• job: InstallSSHKeyTest
  displayName: 'Install SSH Key Test'
  steps:

  • checkout: none

  • task: InstallSSHKey@0
    inputs:
    knownHostsEntry: ***
    sshPublicKey: ***
    sshKeySecureFile: test_ssh_key
    displayName: Install SSH Key `

Task: FtpUpload canarytest pipleine

---

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.
  Yes

---

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).

[Deekshitha2812]

why there is a change in patch even when the minor is not same??

[rishabhmalikMS]

Patch should be kept as 0 here.