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
Updates Task-lib version, which fixed below issues:
AB#2343402
AB#2343422

Task Name

Name of the updated or newly created pipeline task.
ExtractFiles

Description

Summarize the changes made in this PR clearly and concisely.
Updates task-lib version, which contains fix chnages. PR: microsoft/azure-pipelines-task-lib#1146

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

Tech Design / Approach

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

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.).
Canary Pipelines:

1. https://dev.azure.com/canarytest/PipelineTasks/_build/results?buildId=244374&view=results
2. https://dev.azure.com/canarytest/PipelineTasks/_build/results?buildId=244373&view=results

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.

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

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