IPv6 support for the AWS Metadata filter

[tuxlife]

Is your feature request related to a problem? Please describe.

We use an IPv6 EKS cluster in AWS. However, the AWS Metadata Filter cannot be used in this cluster because only the IPv4 (XXX) is used here for requests and not the IPv6 (XXX_

Describe the solution you'd like

In addition to the existing IMDS version, it should also be possible to select whether the metadata server should be addressed via IPv4 (default) or via IPv6.

Describe alternatives you've considered

It may also be possible to automatically detect whether the metadata server is accessible via v4 or v6.

Additional context

[2024/05/07 09:51:55] [ warn] [net] sync io_read #472 timeout after 1 seconds from: tcp://169.254.169.254:80
[2024/05/07 09:51:55] [error] [http_client] broken connection to 169.254.169.254:80 ?
[2024/05/07 09:51:55] [error] [filter:aws:aws.3] Failed to get instance ID