Fix PowerShell Boolean casting issue in Execute method

[kaczynskim]

This PR corrects a misleading example in the PowerShell example for the PackageInfo.Execute method usage.

Issue:
In PowerShell, passing "false" (a string) instead of $false (a Boolean) incorrectly evaluates to $true.

Fix:
Updated documentation to clarify that false should be passed as $false (Boolean) instead of "false" (string).
Ensured that examples use the correct Boolean syntax to prevent execution mode misconfigurations.

Impact:
This fix ensures that users do not unintentionally enable 32-bit execution mode due to incorrect PowerShell type casting.

Reference Issue:
PowerShell automatically evaluates non-empty strings as $true, causing Execute("false", $envRef) to behave incorrectly.
Expected usage should be Execute($false, $envRef).

Please review and approve.

[prmerger-automator]

@kaczynskim : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit e9d83dd:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/integration-services/ssis-quickstart-run-powershell.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[v-dirichards]

@chugugrace Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[rwestMSFT]

Thanks for your contribution. I'm merging this PR as it looks correct.

[prmerger-automator]

PR 10044 has been merged from kaczynskim:patch-1 to MicrosoftDocs:live by rwestMSFT.

@kaczynskim, @chugugrace