Implementing All Responses

[Seltraeh]

I'm looking to automate all responses and link them to their proper handlers.

My original goal was to parse all responses inside all handlers but @Tom2096 reminded me why that's a terrible idea. Some data is required to be specific and by using an integer instead of a unit ID could cause a crash, and any other similar instances of an incorrect value but correct typing.

I'll be:

1. Extracting all responses with best guesses on data typing and game client native naming scheme (prevents stuff like userInfo.cpp appearing multiple times in our code base)
2. Implementing them one by one or working with @arves100 to do each handler one by one as I encounter something too complicated.
3. Understanding how/what MSTs are handling for the server so I'm not overloading the client through the server.
4. Clean-up? Make the server efficient and gracefully handle this new data in an organized way.

[arves100]

1. I do agree with using the game native scheme if we accept the tradeoff that some stuff might be cryptic to read
2. Would be good to implement them as new features are added, like there is no reason for a Friends stub handler now
3. You can check UserInfo handler and Initialize handler for the list of MSTs + ServerCache.cpp for the precomputed MST