Send precise set of addresses to peers on identify

Nobody has claimed this yet.

When sending addresses to a peer we should only send those addresses that are relevant to the peer and not all of our available addresses.
Only send localhost addresses on connections where the remote address is a localhost address
Only send private addresses on connections where the remote address is a private address
Send public addresses to everyone

For this to be effective we'll have to send different signed peer records to different peers depending on the connection that we have.

This filtering is done on the receive side since https://github.com/libp2p/go-libp2p/pull/2300/files. We should also do this on the sending side and not share the node's private addresses with everyone.

It may be possible to get a more precise set of addresses for a peer with a private remote address by consulting the system routing table. I have not thought through the details of this scheme, but majority of cases will have just one gateway and the above system is a good start.

Start by tracing the identify sending path and comparing it with the receive-side address filtering introduced in pull request #2300. Determine how signed peer records can vary by remote address, then verify that localhost and private addresses are restricted while public addresses remain available to all peers.

Written by the indexing model from the issue text.