[Bug]: [AV False Positive] PowerShell OSC 133 integration triggers 'PowerShell/Bypass.K' EDR flag

### Operating system

Windows

### Orca version

_No response_

### Details

### Description
The PowerShell 7 shell integration script uses `-EncodedCommand` with Base64 to handle OSC 133 sequences (`# Orca OSC 133 shell integration for PowerShell`).

In managed corporate environments, Enterprise EDR / Antivirus solutions flag this execution pattern as suspicious under the `PowerShell/Bypass.K` heuristic rule due to the uninspected Base64 execution in memory.

### Environment
- **OS:** Windows 11 / Windows 10
- **PowerShell Version:** PowerShell 7.x (`pwsh.exe`)
- **Detection Type:** Antivirus / EDR Alert (`PowerShell/Bypass.K`)

### Decoded Script Trigger
```powershell
# Orca OSC 133 shell integration for PowerShell...

### Expected Behavior
Shell integration should execute cleanly without triggering EDR or Antivirus heuristic blocks.

### Suggested Fix
Avoid passing integration logic via Base64-encoded strings (-EncodedCommand) on Windows. Consider using standard script files (.ps1) or unencoded arguments to prevent false-positive alerts in enterprise environments.

Start with the PowerShell 7 shell integration script identified as “Orca OSC 133 shell integration for PowerShell” and trace how -EncodedCommand is used for OSC 133 sequences. Reproduce the integration on Windows 10 or 11 with PowerShell 7 and an EDR or antivirus check; done means the integration still works without triggering the reported PowerShell/Bypass.K alert.

Written by the indexing model from the issue text.