fix(inputs.http_response): Fix for IPv4 and IPv6 addresses when interface is set

[zak-pawel]

Summary

This PR solves the problem that existed in the scenario where the urls list contains mix of IPv4 and IPv6 addresses and the interface is config file set.
Until now, the plugin chooses the first available address for the given interface. In my case, it was IPv6 for Windows and IPv4 for Linux. Because of this, the plugin worked incorrectly with IPv4 addresses for Windows and IPv6 addresses for Linux.

Here is a list of the most important things done in this PR:

• Each URL now has its own httpClient (until now, one httpClient was used to handle all URLs).

• Each URL provided in the config and each address for the given interface in the config is parsed and checked to see if it is an IPv4 or IPv6 address.

  • I didn't find methods in the standard library (or in other dependencies) that would do this correctly and handle both url.URL and net.IPNet. That's why I added github.com/seancfoley/ipaddress-go lib. The topic of parsing addresses is complex enough that I didn't see the point in doing it myself. If any of the reviewers have an idea on how to do this better, I would be happy to hear it :)

• Each URL has a httpClient assigned that matches the address format (IPv4 or IPv6).

• Configuration checking and initializing defaults have been moved from Gather to Init.

  • This changes the behavior of the plugin slightly, which will now fail immediately if:
    • parsing the regular expression from h.ResponseStringMatch fails
    • at least one of the URLs provided in the config cannot be parsed
    • at least one of the URLs provided in the config is not of type http or https
    • another problem occurs while creating the httpClient for the URL

  (previously, these errors could occur in Gather, which did not cause the plugin to fail, but rather resulted in recurring errors in the logs)

Thanks to this PR, the http_response plugin tests for Windows are re-enabled.

Checklist

• No AI generated code was used in this PR

Related issues

resolves #8451

[srebhan]

Awesome work @zak-pawel! Just a few small comments...

[telegraf-tiger]

Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip.
Downloads for additional architectures and packages are available below.

⚠️ This pull request increases the Telegraf binary size by 1.62 % for linux amd64 (new size: 243.6 MB, nightly size 239.7 MB)

📦 Click here to get additional PR build artifacts

Artifact URLs

DEB	RPM	TAR GZ	ZIP
amd64.deb	aarch64.rpm	darwin_amd64.tar.gz	windows_amd64.zip
arm64.deb	armel.rpm	darwin_arm64.tar.gz	windows_arm64.zip
armel.deb	armv6hl.rpm	freebsd_amd64.tar.gz	windows_i386.zip
armhf.deb	i386.rpm	freebsd_armv7.tar.gz
i386.deb	ppc64le.rpm	freebsd_i386.tar.gz
mips.deb	riscv64.rpm	linux_amd64.tar.gz
mipsel.deb	s390x.rpm	linux_arm64.tar.gz
ppc64el.deb	x86_64.rpm	linux_armel.tar.gz
riscv64.deb		linux_armhf.tar.gz
s390x.deb		linux_i386.tar.gz
		linux_mips.tar.gz
		linux_mipsel.tar.gz
		linux_ppc64le.tar.gz
		linux_riscv64.tar.gz
		linux_s390x.tar.gz

[srebhan]

Thanks @zak-pawel!

[Mic92]

This seems to break the case when the address is a hostname (in my case pointing to an ipv6 address) instead of an ip address:

Error running agent: could not initialize input inputs.http_response: cannot create local address for interface "tinc.retiolum" and server address "http://transmission.r/transmission/web/"