Invalidate the Fixed Function State on glPopMatrix

Under a sequence like:

  // Render some geometry

  glMatrixMode(GL_PROJECTION);
  glPushMatrix();
  glOrtho( /* for rendering a HUD/overlay in screen space */ )
  // Render the overlay
  glPopMatrix();

  // Render some more geometry

... I found that the glOrtho call was unexpectedly affecting the
rendering of subsequent geometry.

I traced it down to a issue in the Regal code, where the fixed function
emulation shader uniform state was not being invalidated when performing
the glPopMatrix, so it would go on using the incorrect matrix.

Note this also affected other matrix modes, not just GL_PROJECTION.

This patch is the one line fix needed to invalidate the state so the
proper matricies are loaded.

Sorry, I didn't feel like adding a whole new unit test file for a one
line change.
Resolve gcc compiler warnings
Initial REGAL_SYS_ES1, REGAL_SYS_ES2 and REGAL_SYS_GL for compile-time support for ES 1.x, ES 2.x or deskop back-end GL support.
Use standard Python convention for the entrypoint.

Python is not a Java - no need to use classes where
they are not needed. The __main__ convention makes
it easier to locate entrypoints for experienced
Python users, and also allows to use Export.py as a
library.
Initial pass-through ES1 support.
Regal::Emu::So optimizations.
Extend Regal::Emu::Iff fixed-function emulation to raster-pos and window-pos.
Extend RegalHelper helper::size::get to desktop enums.
Trim extraneous whitespace.