(affects OpenGL) Move beginFrame calls to fix fence lifetime.
(affects OpenGL) Move beginFrame calls to fix fence lifetime.

There are a couple reasons for this change. First of all, creating a
Vulkan fence outside of beginFrame / endFrame is not ideal because
the backend does not know yet which command buffer will be chosen
during swap chain acquisition.

Secondly, the Renderer currently calls endFrame in this order:

    frameInfoManager.endFrame
    mFrameSkipper.endFrame
    driver.endFrame

However the beginFrame calls were ordered like this:

    frameInfoManager.beginFrame
    driver.beginFrame
    mFrameSkipper.beginFrame

This change makes it such that the beginFrame calls have the reverse
ordering of the endFrame calls, which is less surprising.

I did a poor man's sanity check by running textured-object on a Pixel 2,
(which enables dynamic resolution) and hacking PostProcessManager to
make it visually obvious if anything were amiss.

google/filament,google/filament,google/filament,google/filament,google/filament,google/filament,google/filament,google/filament,google/filament,google/filament,google/filament,google/filament