LBRY daemon and DHT network status checks

Nobody has claimed this yet.

## The Issue
This is the daemon side issue for: https://github.com/lbryio/lbry-app/issues/603 - the discussion was to have these checks performed on the daemon and added to the [lbrynet status](https://lbryio.github.io/lbry/cli/#status) results.

As a LBRY user, I want to make sure that my PC and network configuration allows for the sharing and consuming content. We should have some type of indicator which checks connectivity on the daemon TCP port (3333) and the DHT UDT port (4444).

For content sharing to properly work, hosts need port 3333 accessible and open to the internet. If the port is not forwarded correctly, their PC won't be able to host but it may still be able to reach out to the reflector servers. If something is blocking port 3333, it won't be able to reach out to the reflector servers, so the content won't be available at all.

For content consumption to work, LBRY needs to be able to connect to the DHT network to find peers. If something is blocking the port, the user experience is really poor - all downloads/streams will hang. There is no indication that something is wrong or needs to be changed.

Probably need an easier way to set these ports, or have LBRY try other ports to see what works.

Background: I've run into a couple users whose ISP blocks port 4444 and they were not able to stream until the port was changed to something else. We also have users who run mining software on port 3333, so if this is taken up by the network, they won't have a proper daemon connection.

Start with the lbrynet status results and the daemon networking paths responsible for TCP port 3333 and DHT UDT port 4444. Review the linked lbry-app issue for context; done means status reports whether both connectivity checks succeed and users have an indication when ports or network configuration prevent sharing or consumption.

Written by the indexing model from the issue text.