Adding EnableVerboseLogging FF

[v-abhishera]

Context Including verbose as an additional argument in the task did not display the print statement for inline SQL. #21025

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

---

Task Name SqlDacpacDeploymentOnMachineGroupV0

Name of the updated or newly created pipeline task.

---

Description Adding verbose as in additional argument to the task will show the print statement for inline SQL, provided that the EnableVerboseLogging feature flag is enabled and verbose is included as an additional argument.

Summarize the changes made in this PR clearly and concisely.

---

Risk Assessment Low

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

---

Change Behind Feature Flag Yes

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 No

Indicate whether related documentation needs to be updated.

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

---

Unit Tests Added or Updated 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, by disabling the FF

• 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