feat(operations.git): support port and ssh://, https:// URLs

[maisim]

The regex in git.repo only parsed SCP-like URLs (user@host), failing on ssh://user@host:port/path and https://host/path formats. Extend parsing to cover these variants and pass the detected port to ssh.keyscan instead of defaulting to 22.

• Pull request is based on the default branch (3.x at this time)
• Pull request includes tests for any new/updated operations/facts
• Pull request includes documentation for any new/updated operations/facts
• Tests pass (see scripts/dev-test.sh)
• Type checking & code style passes (see scripts/dev-lint.sh)
• Pull request title follows the
  conventional commits format

[wowi42]

Sorry for the late review.

Needs discussion before merge.

The PR extends git.repo URL parsing so ssh_keyscan=True extracts host and port from ssh:// and https:// URLs. The change is focused and CI passes, but the interaction between ssh_keyscan and HTTPS URLs is unclear.

Issue: when src is https://host/path, the PR runs ssh-keyscan against that host. ssh-keyscan is for SSH host keys, not HTTPS. For HTTPS clones the keyscan is irrelevant, and defaulting to port 22 instead of 443 is confusing. Either keyscan should be limited to SSH-family URLs (git@host, ssh://), or the PR body should explain why HTTPS triggers an SSH scan.

Also, the PR branch is based on 410d5f92, which is well behind current 3.x. It will need a rebase before merge.

Minor notes:

• src/pyinfra/operations/git.py:149: m.lastindex and m.lastindex >= 2 can be simplified to if m.group(2):.
• The \[? ... \]? in the SSH regex does not actually parse IPv6 addresses.