Add integration test for Get-SqlDscTraceFlag command

[Copilot]

• Explore repository structure and understand existing patterns
• Identify missing integration test for Get-SqlDscTraceFlag command
• Analyze existing integration test examples to understand structure
• Understand build and test workflow requirements
• Locate where integration tests are configured in azure-pipelines.yml
• Create integration test file following established patterns
• Add test to azure-pipelines.yml in group 2
• Test the new integration test locally
• Update CHANGELOG.md
• Address review feedback: fix task name and update README.md

Successfully implemented integration test for Get-SqlDscTraceFlag command and addressed review feedback:

Review Changes Made:

• Fixed error message in integration test to use 'noop' task instead of 'build'
• Added Get-SqlDscTraceFlag to the integration test dependency table in README.md with correct dependencies (run order 2, depends on Install-SqlDscServer and Prerequisites, uses DSCSQLTEST instance)

Added Files:

• tests/Integration/Commands/Get-SqlDscTraceFlag.Integration.Tests.ps1 - Comprehensive integration test covering both parameter sets (ByServiceObject and ByServerName), error handling, and edge cases

Modified Files:

• azure-pipelines.yml - Added the new test to group 2 alongside other Get-* command tests
• CHANGELOG.md - Documented the addition in the Unreleased section
• tests/Integration/Commands/README.md - Added dependency information for the new integration test

Test Coverage:

• Tests both parameter sets: ByServiceObject and ByServerName
• Validates return type (array of UInt32 or empty)
• Tests error handling for invalid instances
• Compares consistency between parameter sets
• Follows established patterns from other integration tests
• Uses correct SQL Server instance (DSCSQLTEST) and credentials for CI environment

The integration test ensures the Get-SqlDscTraceFlag command works reliably in real SQL Server environments and follows the same patterns as other command integration tests in the repository.

Fixes #2216.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

This change is 

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94%. Comparing base (11d39a0) to head (af2d523).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@         Coverage Diff          @@
##           main   #2247   +/-   ##
====================================
  Coverage    94%     94%           
====================================
  Files       149     149           
  Lines      9174    9174           
====================================
  Hits       8698    8698           
  Misses      476     476           

Flag	Coverage Δ
unit	94% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}