time.{h,cpp} -> worldtime.{h,cpp}

why? because posix. you'd think that i wouldn't need to worry about ever
conflicting with anything, because I'd be at my own include path, right?
apparently not, as i did just that on some persons system (and somehow
not my own??!). which really makes me wonder what's a more scaleable solution
than "rename the conflict to something not".

asking everyone i know, looking around basically everywhere, leads
people who either never heard of the issue, think that < > vs "" includes
will somehow fix it (even though i know which to use properly and when),
or that setting the include prefix will help, and gcc docs say it
may or may not be listened to anyways.

seems that everybody just works around it via a case by case rename.
one could do e.g. ore_timer.h, etc....but seems a bit silly. surely
i'm overlooking something? how can any of this scale? there's got to be
a million people installing something like mytimer.h, or object.h...
or matrix.h...and it's all got to conflict, doesn't it?

only tangible results i got were from the haxe guys, who have/had the
same problem and apparently resolved it via this commit-esque
fix moc issue(regression from cmake change that didn't break on my sys)

use const_cast to workaround 5.3 bug for now, until this code gets
replaced/fixed proper
Add a method in Debug to check if an area is enabled, by enum number.

This will lets us get rid of the old debug area enabledness stuff from
the Settings class.
Get rid of Settings::debugAreas and methods using it.

There is now only one place that stores what debug areas are enabled:
the QLoggingCategories themselves.
Minor cleanup in debug code.
Change how logging categories are enabled and disabled.

Store a QSet with our own idea of what logging categories are enabled,
and install a categoryFilter that looks at that set to enable and disable
the categories for real. This is necessary because a category filter is
really the only place that legitimately gets a non-const QLoggingCategory,
and thus the only place where we can call setEnabled.
Remove const_cast hack in the category map.

We can now store const QLoggingCategory's.
Remove comment about removed hack.

I forgot to do it in the previous commit.
isAreaEnabled: use our set instead of looking at the actual category.
Don't mess with the default logging category.

The logging code was inadvertently turning off the 'default' logging
category, which would hide messages from the QML/QtQuick runtime.
Make *areaEnabled(int area) a wrapper for *(QString categoryName).

This will let us replace uses of the former in favor of the latter and
eventually get rid of the old area enums and the map between enums
and categories.
Add {set,is}AreaEnabled wrappers taking QLoggingCategory.

This lets callers do stuff like setAreaEnabled(ORE_AUDIO(), true).
Port settings dialog to use category names to enable/disable logging.
Merge branch 'master' into custom-physics

Conflicts:
	src/debug.cpp
	src/settings/settings.cpp