Provide for workaround for internet validation (ping)

[cocarrig]

Description:
For network validation, the DAKboard OS completes a ping request to validate internet access. Because some organizations block outbound ping requests there is a use case for the ability for the users with terminal access to change the destination ping address in one location as opposed to the current hardcoded multiple locations.

[cocarrig]

potential redesign methodology using netcat:
nc -vz google.com 443

• if fails continue
  nc -vz dakboard.com 443
• if fails take legacy actions for failure to ping

command success criteria:
'succeeded' is present in response

[Dan-Peck]

After some initial research, nc appears to never exit when there's a failed connection, and while we can specify the length of timeouts, there is no way to specify the number of retries!

However, there is a CLI unix utility called timeout that can kill a process after X amount of time. I've tested this and it works nicely! The exit status can be used to determine the success of the operation. If it is 0, then it was a successful test, anything else, and it is a connection failure.

[cocarrig]

Completed and released in version 4.01 for RPi models, will not be supported for OPi models at this time:
https://github.com/dakboard/Hardware-OS/releases/tag/4.01