Review connection read/write error logic about aioslsk HOT 5 CLOSED

For the obfuscated flag bug, instead of starting the reader loop as soon as the connection state goes to CONNECTED the peer initialization message is now handled first, the connection gets modified and on then PeerConnection.set_connection_state with ESTABLISHED us called which now starts the reader loop.

from aioslsk.

PeerConnection was modified not to cancel the reader task and instead just to let the task run its course; the loop stops when the state of the connection goes to CLOSING/CLOSED. The task gets cleaned up after all disconnect tasks have been complete and messages still received during closing will be ignored.

from aioslsk.

Additionally the MR resolves another bug:

By default on login messages would be sent to notify the server that we have no parent but this isn't necessarily true if we just lost connection to the server (and not the parent) and reconnect.

Now a LoginEventSuccess is emitted by ServerManager and picked up by PeerManager which reports the correct messages to the server when login is successful by looking if we still have a parent

from aioslsk.

Refactored some of the message (de)serialization code. Which was necessary to handle exceptions when waiting for peer init message

from aioslsk.

It's fine for now, I did see an error where the ticket could not be found in the _expected_connection_futures and it was unclear why this happened (everything looked fine).

from aioslsk.