Fix for AzureCLIV3

[v-schhabra]

When the UseAzVersion feature flag is enabled, the AzureCLI@2 task runs 'az version' instead of 'az --version'. In some environments, 'az version' returns exit code 0 but with empty stdout, causing the version parsing to fail.

The existing fallback logic only checked for non-zero exit codes or stderr output, but didn't handle the case where stdout is empty or contains only whitespace. This fix adds checks for empty stdout to trigger the fallback to 'az --version', ensuring the task works reliably.

---

Task Name

AzureCLIV2

---

Description

Summarize the changes made in this PR clearly and concisely.

---

Risk Assessment (Low / Medium / High)

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

---

Change Behind Feature Flag (Yes / No)

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

---

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.

---

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

---

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

---

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

[sanjuyadav24]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).