Vibe code --follow-symlinks

[andyleejordan]

Fix #5169.

[andyleejordan]

Did it work?

[Copilot]

Pull Request Overview

This PR fixes issue #5169 by updating the build and packaging scripts to always use symbolic links for the PSES modules.

• Removed conditional handling for Debug and Release builds in the RestoreEditorServices task to enforce symlink usage.
• Updated the package script in package.json to include the --follow-symlinks flag to support this change.

Reviewed Changes

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

File	Description
vscode-powershell.build.ps1	Removed the configuration-based switch and now always creates a symbolic link for PSES.
package.json	Added the --follow-symlinks flag to ensure packaging respects symbolic links for modules.

Comments suppressed due to low confidence (2)

package.json:108

• [nitpick] Consider updating the project documentation or release notes to explain the new '--follow-symlinks' flag and its impact on the packaging process.

    "package": "vsce package --out out/ --no-gitHubIssueLinking --follow-symlinks",

vscode-powershell.build.ps1:36

• The removal of the configuration-specific switch is a significant change. Please confirm that always using a symbolic link for './modules' is intended and update the code comments or documentation to clarify this behavior.

    # Always use a symlink for ./modules pointing to PSES

[andyleejordan]

This "vibe code" attempt was via the Copilot agent inside a pre-populated codespace for the issue, but now that it's enabled for the PowerShell GitHub organization, I'm having it re-attempt using "assign to Copilot agent" in #5212.