Copy announcement message addresses into NodeInfo on load

[TheBlueMatt]

On startup, we may deserialize a stored NodeAnnouncement and find new address types that we previously didn't understand. This will leave us with a NodeInfo struct (the obvious place users will look for address information) that has an addresses list that is missing elements.

Additionally, we're storing address information twice in two separate, redundant, heap-allocated structures.

We should address both issues by simply dropping the address list from NodeInfo. The only two gotchas are that we'll want to provide serialization compatibility, and that we'll want to ensure we're liberal in storing NodeAnnouncements as long as they have even a mostly-reasonable excess data size. We should probably take this opportunity to also relay NodeAnnouncments that have more excess data than zero.

[ssbright]

Hey, I am new here and would like to start getting involved. I am going to start looking into this issue and see what I can understand.

[TheBlueMatt]

Slipping, not worth holding 112 for it. Let us know if you're still interested in working on this or want suggestions @ssbright.

[ssbright]

Apologies for the poor communication. I tried working on this but found that my rust skills were not adequate enough. I will have to start somewhere more simple to learn how to contribute to open source. Hopefully someone else can tackle this issue. @TheBlueMatt

[TheBlueMatt]

Dropping form milestones. Its not really a huge deal, and its now been long enough since 111 that its not worth trying to move "quickly" here. Still should be addressed and would still love for someone to take this on, though!