Can't properly check client version

[Iamgoofball]

PROBLEM: We can't check the client's version beyond whether they're using AO2 or not. This roadblocks adjusting anything that impacts messages going to the client, since we now can't properly develop backwards compatibility for older clients and would have to simply reject their connections and force everyone to update.

Examples of why this was an issue:

1. The check for whether it should send the features list to the client would break upon the client version progressing past 3.X.X or higher.
2. We aren't able to extend the client messages system or rework/reorder it in any way, shape, or form without breaking older clients.

SOLUTION: Implement a more robust version checking function on the Client class, with a variable to hold the version list alongside a wrapper proc to handle checking the version. This has been done in the following pull request https://github.com/AttorneyOnlineVidya/tsuserver3/pull/15

[argoneuscze]

Please split the two, since they're entirely different features.

[Iamgoofball]

This has been done.