[GL Overlays] Initial Commit (w/ double buffer & AA disabled)

Committing what I have figured out, may abandon this idea.  I run into a
bizarre performance issue with double buffering on.  FRAPS reports 60FPS
but it is definitely not.   CPU is also 2x higher than without double
buffering.
[Fix] Crash with new CVS display
Merge remote-tracking branch 'origin/dev/2.0' into feature/gl-overlays
[GL Overlays] Further refactoring

Original functionality restored, including working AA along with double
buffering.  Required disabling the automatic management of buffer
swapping.
[GL Overlays] Fix glitchy screen during init & first resize
[GL Overlays] Actually fix glitchy screen on init

Still didn't work on release builds, which appear to fill the buffer
with random GPU data on init
[GL Overlays] Test moving to drawBackground

Foreground will still not display unless GLWidget is hidden...
[Messaging] Better behavior involving Qt::IsItemEditable

The program was doing a lot of questionable things.  It didn't need to
send activate() to edit(), and the NifDelegate was bypassing the item
flags / edit behavior for Spells and bool types
[Messaging] Remove QT_NO_DEBUG / qWarning combo

It's equivalent to just use qDebug() since the project is built with
QT_NO_DEBUG_OUTPUT.

Fix QT_NO_DEBUG_OUTPUT typo.  :neutral_face:
[Fix] Save Image crash in MSVC Release mode, Qt warning

Fixes a crash that occurred in MSVC builds only, only in Release mode.
Qt warning started appearing after putting GLView inside of a
QGraphicsView, so changed QDialog's parent for screenshot dialog.
Merge branch 'task/messaging-refactor' into dev/2.0
[Messaging] Change inappropriate qWarnings to qDebug

These were all meant to be debug output in the first place.
Merge pull request #1 from jonwd7/dev/2.0

Dev/2.0