[FEATURE] Add Support for PowerShell Scripts

[izzalDev]

---

Is your feature request related to a problem? Please describe.
I'm always frustrated when working in environments where PowerShell is the preferred shell, but only batch files (.bat) are supported for automation. This limits flexibility, readability, and access to advanced scripting features provided by PowerShell, such as robust error handling and object manipulation.

---

Describe the solution you'd like
I would like the system to fully support PowerShell scripts (.ps1) as an alternative to batch files. This includes:

• Allowing PowerShell scripts to replace or supplement existing batch files.
• Ensuring that scripts are executed correctly with any required permissions or prerequisites (e.g., setting the execution policy).
• Providing documentation or examples for users to transition or start using PowerShell for automation tasks.

---

Describe alternatives you've considered

• Converting batch scripts to PowerShell manually for internal use, but this approach is cumbersome and lacks official support.
• Using third-party tools to invoke PowerShell scripts from batch files, which introduces unnecessary complexity.

---

Additional context
PowerShell provides modern scripting capabilities and is cross-platform, making it a better long-term solution compared to batch scripts. Supporting PowerShell will benefit users who rely on advanced scripting for tasks, especially in environments where Windows or cross-platform compatibility is essential.

[FaceFTW]

As someone who is going to try out dotter, one way I'm thinking around this limitation is to either just invoke pwsh.exe/powershell.exe with the -File argument or just have the entire batch file just be pwsh.exe -Command {/*powershell code here*/}

This is by no means discouraging first-class support for PowerShell on Windows. I might work on this feature depending on how painful I find the workaround to be.