Add changes for kudu warm up

[kumaraksh1]

Context

Describe the context or motivation for this PR. Include links to any related Azure DevOps Work Items or GitHub issues.

---

Task Name

AzureWebApp

---

Description

Introduced a new API that in azure pipeline common tasks - microsoft/azure-pipelines-tasks-common-packages#568

This will be called before any deployment to make kudu container available.

Risk Assessment (Low / Medium / High)

Low.
This is to optimize the deployment and everything is in try catch.

---

Change Behind Feature Flag (Yes / No)

Can this change be behind feature flag, if not why?
There is no need to add this behind feature flag.
There was a previous API, instead of that we will be calling new api.. its not going to create any error in deployment.
Its just optimization

Tech Design / Approach

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

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

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

---

Unit Tests Added or Updated (Yes / No)

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

---

Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).
Tested the changes on a prod canary app by pushing the task in my testing feed.
https://dev.azure.com/kumaraksh/Test/_build/results?buildId=85&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=7ead7f30-9997-5ce5-fb3b-d8df586a067d

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).
  Added debug logs and only needed.

---

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

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.
  We just to revert this task.

---

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.
  No other module will be impacted because of this.

---

Checklist

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