Provides support for configuring Aspects from file. 

Provides support for Configuration Aspects. ThaumcraftEntity is a generic object for wrapping read/write friendly aspects for each entity.
Configuration is under Config/ThaumcraftMobAspects. Each entity is divided into categories (based on ModID) with a seperate file for each.
Example groups: vanilla, vanillaitems, unknown.

Players are currently placed into 'unknown' as EntityList does not contain a player entity there is no way to know if the entity doesn't exist or is a player.
NBT support could be added by adding a NBT array object in ThaumcraftEntity. AFAIK, GSON is perfectly happy ignoring non-existent fields so its easily optional.

JSON does not allow comments: everything must be data. Comments in the configs are handled by actually placing them in the Java fields, i.e. _HEADER, _FOOTER, and _COMMENT.

Moved registration from load to post to allow for entities to registration. I can't see any benefit to doing it earlier, but can be easily reverted if desired. I feel I should note that the  "required-after:Thaumcraft;after:MoCreatures;after:LycanitesMobs;after:SpecialMobs" could be changed to the more generic "required-after:*" to be the last one to load.

DISCLAIMER: Never tested outside eclipse. This was a useful test case to see how GSON handles and get a feel for the workflow. As such testing outside file read/writing are practically non-existent.