feat: Separate socket code into a separate layer from connection layer

[XavierChanth]

Connection currently has two responsibilities:

• Ensuring a connection to the atServer/atDirectory is established and up (orechestration of sockets)
• Doing elementary, platform specific socket operations as part of the orchestration.

I will split out this latter part into it's own layer to do things like:

• read from a socket, and managing errors
• write to a socket and managing errors
• create a socket connection
• dispose of a socket connection
• check if a socket is up (possibly, will need to evalute which layer this is best done at)

Separating these 4 or 5 operations will make it easier to switch between implementations for different platforms and socket libraries.

[XavierChanth]

This also gives us another surface for testing socket stability, which is something the c sshnpd beta currently struggles with. We can then determine if it is something elementary to the socket implementation, or if it is something further up the stack.

We can also build stress tests for the implementation which can put more pressure on the sockets than an atServer does.