Enable upnp in libp2p

[dtynn]

Hi, would like to know if changes in  #4057 feat(p2p): enable UPnP to improve reachability are helpful for subspace nodes & farmers in some situations.

You can see the diffs on my own fork.

I've already check the libp2p version in both projects, and there should be no compatible problems.

Remind me if you want a pr for this~ 😉

[nazar-pc]

Honestly I'm reluctant to having UPnP support and would rather prefer users creating static port forwarding manually instead.

UPnP is a very insecure protocol and anyone who cares about security should disable in their router anyway.

@shamil-gadelshin do you have a strong opinion about this?

[shamil-gadelshin]

Users don't change the default router settings in most cases. And it seems that upnp became disabled by default in modern routers because of security concerns as Nazar mentioned. It seems a nice feature to have because it can improve the overall connectivity of the network, however, I agree that if the user needs a router settings change it's better to have port forwarding instead. Also, this change would require extensive testing with the network scan to prove that the number of available addresses increased after the change.

[nazar-pc]

@dtynn thanks for suggestion, but I think we will not introduce UPnP support, at least for now. We do plan to have hole punching through NAT more generally at some point, which will have a similar benefit, see #1022