Fix custom port handling in remote security scans

[shadowbipnode]

Remote security scans currently do not consistently honor targets that include an explicit port, such as sftpcloud.comdata.it:2022 or https://example.com:8443.

Expected behavior:

• Parse host and port from host:port and URL inputs.
• Infra Intel should scan explicit target ports.
• SSH Audit should use the explicit port instead of assuming 22.
• TLS Check should use the explicit port instead of assuming 443.
• HTTP/HTTPS probes should preserve explicit ports.
• Target normalization should support host, host:port, http(s)://host, http(s)://host:port/path.

This is a bugfix for the v1.7.x release line.