Fix SSH config parsing failure when Match directive precedes Host blocks

[Copilot]

russh-config does not support the Match keyword — encountering it before the first Host block causes the parser to return HostNotFound, making sshping fail entirely. Moving Match directives to the end of the file was the only workaround.

Changes

• strip_match_blocks(contents: &str) -> String — preprocesses raw SSH config content by dropping every Match line and all option lines belonging to that block (up to the next Host or Match keyword). Comments and blank lines inside Match blocks are also dropped.
• parse_config_path(path, host, context) — wraps file reading + strip_match_blocks + russh_config::parse(). Replaces all three parse_path() call-sites (main config, jump host config, ProxyCommand config).

Example config that previously failed

Match host * exec "gpg-connect-agent UPDATESTARTUPTTY /bye"

Host myserver
    User alice
    Port 2222

The Match block and its settings are stripped before being handed to russh-config, leaving valid Host-only content to parse.

[codacy-production]

Not up to standards ⛔

🔴 Issues 2 medium

Alerts:
⚠ 2 issues (≤ 0 issues of at least minor severity)

Results:
2 new issues

Category	Results
Complexity	2 medium

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}