docs(windows): document unsupported native tooling

[lisandrorivero-tes]

Pre-flight Checks

• I have searched existing issues and this is not a duplicate
• I understand this issue needs maintainer approval before a PR can be opened

Problem Description

Issue #157 was closed as out of scope for a maintained native Windows helper, but the research is still useful for users who want Windows-side tooling. Without a docs-only reference, that knowledge is lost or may be mistaken for a supported installer path.

Proposed Solution

Add an unsupported "Native Windows tooling" section to docs/manual-installation.md that clearly keeps Windows-via-WSL as the supported path while documenting reference-only native Windows setup notes, including:

• Scoop install commands for common tools
• Windows config locations for Alacritty, WezTerm, Neovim, Nushell, and Starship
• Nushell adjustments for Unix-oriented config assumptions
• Terminal configuration notes explaining that Alacritty and WezTerm can launch either WSL or native Windows shells

Affected Area

Documentation

Alternatives Considered

A maintained PowerShell installer/helper was considered in #157, but it was closed as out of scope because it would create a parallel native Windows maintenance path outside the Docker E2E suite.