[Fix] UPnP Discover

[cschuchardt88]

Description

The current UPnP is so old that it doesn't work correctly!!!! Wrote a new UPnP searcher to apply the node's open port on all devices and interfaces.

Type of change

• Optimization (the change is only an optimization)
• Style (the change is only a code style for better maintenance or standard purpose)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Unit tests
• Run Application

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[shargon]

There is no a good external nuget for UPnp?

[cschuchardt88]

There is no a good external nuget for UPnp?

I rather have control of the code myself unless it's Microsoft. Because problems need to be fixed immediately. And less bloat code.

@Jim8y can you test on macOS github vm is failing for macos

[shargon]

In my opinion, we can remove UPnP support. It's something the network administrator should handle. Perhaps they don't want to open the ports to the outside, and we opened them without asking. Besides, it's a complex protocol that's completely unrelated to the node.

What do you think @erikzhang?