Debug mode/verbose logging output

[bloerwald]

@Amaroth requests:

Noggit can crash for various reasons - issues in app itself, or somehow invalid input data. The problem is that common user can't find out what is going on with his map. When you attempt to open a map in Noggit and crash happens, you've got damn lot of figuring out what is actualy causing crash.

I'd welcome feature in settings which would probably include multiple checkboxes, and user would be able to turn debug outputs from all kinds of methods in code on. It would be lot of spam, slowing performance down and creating probably quite large log - I know. Thats why it should create new, dedicated debug log, why it should be turnable on/off (and should be by default off) and why I'd divide it into multiple cathegories (logs from ADT, logs from M2s, from WMOs..."

User would be able to see then "Ah, when I open map, the last thing Noggit does is that it attempts to load xyz.wmo, and then it crashes. So, that WMO is probably causing issues.". Having such feature would prevent us from throwing away many, many malfunctioning projects in past, until now, we were just forced to start over or revert to some often old backup. This would also help us with distinguishing between Noggit errors and invalid input data errors.

which effectively requests a lot more debug logging and more usable error messages.