Report PowerShell 5.x module operation failures instead of success

[Gabriel Dufresne (GabrielDuf)]

This pull request improves error handling in PowerShell package operations by ensuring that non-terminating errors are properly propagated to the exit code, unless the user explicitly overrides error variable handling. It also adds comprehensive tests to verify this behavior.

PowerShell error handling improvements:

• Added a constant ErrorVariableName to PowerShellPkgOperationHelper to standardize the error variable used for capturing errors.
• Modified parameter generation logic in PowerShellPkgOperationHelper to automatically add -ErrorVariable and an exit code check (;if($ErrorVariableName){exit(1)}) unless custom error variable parameters are supplied by the user.

Testing enhancements:

• Added tests to ensure non-terminating errors are correctly propagated to the exit code for all operation types, and that custom error variable parameters are respected and not overridden.

[Copilot]

Pull request overview

Improves PowerShell 5.x package operations so non-terminating errors produce failure exit codes.

Changes:

• Captures cmdlet errors using a standardized error variable.
• Exits with code 1 when captured errors exist.
• Adds coverage for all operation types and custom error-variable handling.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellPkgOperationHelper.cs	Adds error capture and exit-code propagation.
src/UniGetUI.PackageEngine.Tests/PowerShellManagerTests.cs	Tests error propagation and custom parameter behavior.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.