Decrease memory usage when sharing host World state.

[guerro323]

(not related to multiplayer networking)

Right now, serializing a world state take a lot of memory on a real game:

• Some useless data are added (for example Links array that could be totally removed when sending data)
• Archetypes and Component Types information are sent every frame (no caching)

Proposed changes are:

• Remove Component Links write/read, and let the user know which entities are in which ISerializer.
• Cache archetypes and component types information, but I personally think they should be sent in another message (since the client can sometimes not process a frame of data for performance reasons; and this mean we will need to create data for each connected client...)
• Use BitBuffer instead of DataBuffer, which support delta encoding, zig-zag encoding, etc...
• Implement custom serializers (it's already the case, but it's kinda hard to add one) and an easy way to not serialize a component.

[guerro323]

Current Progress:

• Remove Component Links write/read, and let the user know which entities are in which ISerializer.
• Cache archetypes and component types information, but I personally think they should be sent in another message
• Use BitBuffer instead of DataBuffer, which support delta encoding, zig-zag encoding, etc... (I don't think this one will get added)
• Implement custom serializers and an easy way to not serialize a component.