Trim address sets (in the peerstore itself) with more than 10 addresses per transport

Most users should advertise 3-4 addresses:

• localhost (only on localhost conns)
• interface addr
• public ipv6
• public ipv6

We should filter peer addresses in the peerstore if a peer advertises more than 10 addresses for a single transport:

• Prefer public addresses.
• Prefer the address/port we observe on the connection. This may be hard to do in the peerstore? I'm not sure if this is filter is really necessary.
• Prefer addresses that share the same port across an IPv4 and IPv6 variant. That is, if I have /ip4/1.2.3.4/tcp/1234 and /ip6/2000::5/tcp/1234, I should keep those over addresses where I only have an IPv4 or IPv6 address for the port. A shared port is an indication that the address is actually valid.

Really, if the peer advertises more than 10 addresses per transport, I'm fine just dropping a bunch of them.

Start with the peerstore's address handling and transport-specific address sets, then trace how connection-observed addresses are recorded. The issue needs a decided policy and tests showing that sets over 10 are trimmed while public, observed, and shared-port addresses are preferred; otherwise, excess addresses may simply be dropped.