feat: PowerShell Wrapper via cdd init powershell

[hammadmajid]

What problem are you trying to solve?

cdd init supports fish, bash, and zsh only. PowerShell users, on Windows and on Linux and macOS with pwsh, cannot Jump: the binary prints a path but there is no Wrapper to change the caller's directory.

Proposed solution

Add powershell (alias pwsh) to cdd init, emitting a function that starship and zoxide have already proven works:

Invoke-Expression (& cdd init powershell | Out-String)

The emitted cdd function forwards the pass-through subcommands (help, completion, init, scan, version) to the binary, otherwise captures & cdd pick @args, checks $LASTEXITCODE, guards against an empty result, and runs Set-Location -LiteralPath. The pass-through list continues to come from the cobra command tree.

Alternatives considered

• Asking users to write their own function. Defeats the cdd init <shell> contract.

Additional context

• The Picker draws on the tty. On Windows this needs CONIN$/CONOUT$ instead of /dev/tty, and Windows binaries are not built yet. Shipping pwsh on Linux and macOS first is a reasonable first slice, with Windows binaries and GoReleaser targets as a follow-up.
• Ruled out of scope for v0.1.0 on the wayfinder map: Wayfinder map: cdd v0.1.0 #2
• Reference research on the shell init pattern is quoted in the resolution of How starship and zoxide implement shell init for fish, bash and zsh #8