chore: clean up allowlisted IPv6 prefixes

[r-birkner]

For guestOS, the IPv6 prefixes are only used if there are no rules in the registry as a fallback (see here).

For hostOS, the IPv6 prefixes are always used. Here the most important change are the telemetry_clients prefix list, which is necessary for scraping metrics and logs from the host.

In the following, I list the guestOS prefixes with their DC:

"2602:fb2b:120::/48",             # ch1
"2602:fb2b:100::/48",             # dm1
"2602:fb2b:110::/48",             # fr1
"2600:c00:2:100::/64",            # se1
"2001:4c08:2003:b09::/64",        # sh1
"2600:3007:4401::/48",            # tp1
"2a00:fb01:400::/56",             # zh1
"2a00:fb01:400:200::/64",         # zh2
"2a05:d01c:e2c:a700::/56",        # AWS_eu-west-2_monitoring
"2a05:d01c:d9:2b00::/56",         # AWS_eu-west-2_monitoring2

[r-birkner]

I requested a review from:

• @eichhorl just to make sure this does not impact recovery (we only change the default rules in guestOS if the registry is not available)
• @NikolaMilosa to make sure this does not impact observability (both metrics and logs scraping for the host)
• @slawomirbabicz to make sure this is good from security POV

[NikolaMilosa]

LGTM

[slawomirbabicz]

LGTM. If you have some a spare cycles, I would add a comment for the prefixes added about their dc affinity.