fix: set pwsh dvc exec capabilities flag only when pwsh is present

[Vladyslav Nikonov (vnikonov-devolutions)]

No description provided.

[github-actions]

Let maintainers know that an action is required on their side

• Add the label release-required Please cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module) when you request a maintainer to cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module)

• Add the label release-blocker Follow-up is required before cutting a new release if a follow-up is required before cutting a new release

• Add the label publish-required Please publish libraries (`Devolutions.Gateway.Utils`, OpenAPI clients, etc) when you request a maintainer to publish libraries (Devolutions.Gateway.Utils, OpenAPI clients, etc.)

• Add the label publish-blocker Follow-up is required before publishing libraries if a follow-up is required before publishing libraries

[Copilot]

Pull request overview

Conditionally advertises and executes PowerShell 7 DVC support based on executable discovery.

Changes:

• Detects pwsh.exe at DVC startup.
• Gates capabilities and execution using the resolved path.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.