TerasologyEngine, reordering of methods

No functional changes: only reordering of methods. 

First listed are the constructor and supporting methods, now followed by life-cycle methods, game state handling methods, accessor methods and finally methods that didn't fit anywhere. If feasible/meaningful, within each category methods tend to be listed after the methods they support, while in some cases it was possible to keep related methods together even if they cross category-boundaries. Also fixed a small typo.

Crucially, I did not separate the categories with comments such as 

    // ------------------------------------------------------------------------
    // LIFE-CYCLE METHODS
    // ------------------------------------------------------------------------

as I know @immortius is allergic to them and develops painful purple-green rashes on his corneas if he sees them. Instead, I used private methods such as
    
    private void xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx() {} 
    private void LIFECYCLEMETHODS() {}
    private void xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx() {}   

(the number of x varying slightly each time) which have the additional advantage of showing up as neat separators even in the class structure view.           


You thought I was serious for a moment, didn'tcha?