Moved sending packet code to EasySocket.cs

I realized I needed an extra peice of data, the remote IP of the client.
Can read what is in the byte array (converted to hex)

I felt like this was pretty important to note. This can read the packet
from the byte array (by converting the byte array into a hex string).
Writing it out to the console, I saw the
00ffff00fefefefefdfdfdfd12345678, which is equal to MAGIC. Before it,
would be the client id, and the first two characters (01), would be the
Packet ID (PID). The PID SHOULD have been 0x01, and the packet had 01
at the front, so they matched.
More advanced reading the first packet

Working on sending. If sending works, then I will start to organize the
code a lot.
Added sending packets

Doesn't work, and I have no idea why. I don't see a mistake anywhere.
Oh well, perhaps just more testing will have to do. :(
More tests

Okay, I am going to try to skip this packet, and try a different
packet. First, I will clean up some code, to make my life easier.
Started Packet class

To make things a little nicer ;D
Able to add data to a packet
Raw property
Finished new packet class

Making things easier, with classes ;D. Anyway, the thing with this is
that some conversions in Packet.cs is not 100% accurate. I will have to
work on it later to get the back data that is converted.
Merge pull request #2 from GP1/master

Update