fix(net/security): Handle IPv6 zone IDs in link-local addresses

[joshtrichards]

• Problem reported here: https://help.nextcloud.com/t/invalidargumentexception-given-ip-address-cant-be-parsed-with-link-local-address-after-update-to-30-0-1-2/207968

Summary

Link-Local Addresses in IPv6 may contain Zone indexes/IDs (e.g. fe80::1fc4:15d8:78db:2319%enp4s0). Parsing was failing and throwing. This PR fixes that by enabling the handling in our existing IP handling library.

Docs for the library we use: https://github.com/mlocati/ip-lib?tab=readme-ov-file#accepting-ipv6-zone-ids

Wikipedia for the curious: https://en.wikipedia.org/wiki/IPv6_address#Scoped_literal_IPv6_addresses_(with_zone_index)

TODO

• Add tests ideally

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[joshtrichards]

/backport to stable30

[nickvergessen]

Should add tests to all affected components:
https://github.com/nextcloud/server/blob/master/tests/lib/Security/Ip/RemoteAddressTest.php
https://github.com/nextcloud/server/blob/master/tests/lib/Net/IpAddressClassifierTest.php

[MartB]

Indeed, Im going to close my PR then :)