Remove Uninstall parameter documentation from Install-SqlDscServer

[Copilot]

The Install-SqlDscServer command documented an Uninstall parameter in its comment-based help that doesn't exist in the actual parameter block. This creates confusion since uninstall operations should use the dedicated Uninstall-SqlDscServer command.

Changes

• Removed .PARAMETER Uninstall documentation from Install-SqlDscServer.ps1 comment-based help
• Updated CHANGELOG.md

The command never accepted an Uninstall parameter—only the internal Invoke-SetupAction function does. Documentation now accurately reflects the public API surface.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Remove Uninstall parameter from Install-SqlDscServer command</issue_title>
<issue_description>### Problem description

The Install-SqlDscServer command currently has an Uninstall parameter, however, there is already a dedicated Uninstall-SqlDscServer command. This is redundant and may lead to confusion for users. The parameter Uninstall should be removed from Install-SqlDscServer, and the comment-based help should be updated accordingly.

Verbose logs

N/A – This is a code/service design inconsistency, not a runtime error.

How to reproduce

1. Open the module file for Install-SqlDscServer.
2. Observe that it exposes an 'Uninstall' parameter even though there is a separate Uninstall-SqlDscServer command.

Expected behavior

The Install-SqlDscServer command should not have an Uninstall parameter. Users should use the Uninstall-SqlDscServer command for uninstall operations.

Current behavior

The Install-SqlDscServer command currently exposes an Uninstall parameter, which suggests that Install-SqlDscServer can also perform uninstall operations, overlapping with Uninstall-SqlDscServer and potentially causing confusion.

Suggested solution

Remove the Uninstall parameter from the Install-SqlDscServer command and update comment-based help/documentation accordingly so that uninstall actions are only performed using the Uninstall-SqlDscServer command.

Operating system the target node is running

N/A – not node or OS specific, module code/design only.

PowerShell version and build the target node is running

N/A – not node or PowerShell version specific, module code/design only.

Module version used

Main (current development branch) at time of proposal.
```</issue_description>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

• Fixes Remove Uninstall parameter from Install-SqlDscServer command #2397

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

This change is 

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

---

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

[johlju]

@johlju reviewed 2 files and all commit messages, and made 1 comment.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @copilot[bot]).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94%. Comparing base (4904751) to head (0ac06fb).
⚠️ Report is 32 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #2398   +/-   ##
=====================================
  Coverage     94%     94%           
=====================================
  Files        186     186           
  Lines      10238   10238           
=====================================
  Hits        9633    9633           
  Misses       605     605           

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

Files with missing lines	Coverage Δ
source/Public/Install-SqlDscServer.ps1	100% <ø> (ø)

🚀 New features to boost your workflow:

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