Reorganize Player class on server

[coyotte508]

Player class with introduction of reconnect has become a bit convoluted. Plus with the state() and all involved...

I think some subclasses/structs should be created, to store the data and divide the functionality and make everything clearer.

[coyotte508]

For example, one big classes that manages all the Analyzer (the relay classes) or at least the sockets, and their deletion.

The player class can do Orgarnizer::trash(...), and the organizer will deal with it properly, for example waiting that it sent its info before deleting it.