0.5.0

Changed

• Set-RouterSshPortProxyFirewall now also adds a Hyper-V Firewall
  allow (New-NetFirewallHyperVRule) scoped to WSL's VM-creator id, not
  just the Defender rule. On Windows 11 WSL "Hyper-V firewall" mode,
  WSL-to-host traffic is filtered by the Hyper-V Firewall (default-Block)
  and the Defender rule has no effect, so the portproxy was reachable
  from the host but not WSL - failing the Ansible router pre-flight with
  a TCP timeout. Both rules are idempotent and no-op when their
  preconditions are absent.