No Joy
Test case to hang original TI driver BAD canse
Reworked TimingCloudSocketTimeout to be more generic using uint32_t
SPARK_WLAN_SetNetWatchDog(uint32_t timeOutInuS); and testing in the
event loop of the CC3000

Removed isSoketClosed because it prevented a socke the did not connect
by timedout by SPARK_WLAN_SetNetWatchDog from being closed.
Reverted removal of isSocketClosed used in read/ write but removed from
disconnect
Application will Cause Failuer Every 3 coonects
 Result The CC3000 ignores close operations and only used Timeout that
was net in net app.
Removed sacrificial sockes ans they did not help.
removed Setting timouts becaus a close still requiers The inactivity
timer to timout.
Set inactivity timer to 20 Seconds.
Set watchdof to inactivity timer + 250 Ms
Better debug infor from TCPclient and added (SOCKET_STATUS_INACTIVE !=
get_socket_active_status(_sock)); to status call.
Uses inactivity Timer of 20 Sec and Watch dog of 2.250 Seconds
Bad Every n
Application Bad Every loop
 Removed internet test prior to reconnect ans there was no benifit that
justified a goto.
Allow to be good
Detect and report on coherancy issues with the sparkSocket handle
Using 32 second inactiviaty time for now 2 X spark protocol + some