Additional rename-related project file changes.

Xcode made these on its own.
Removed SceneViewControllerFor…#initWithNibName:bundle: initializers

Secondary SceneViewControllerFor…#initWithNibName:bundle: initializers removed.  This is strangely called as part of UIViewController's init implementation, and thus was getting called twice.

The initWithScene: method is the designated initializer, and is now marked as such.
Fixed viewWill/DidLoad/Unload super/WillLoad

`[super …]` calls put in the SceneViewControllerForCG/GLK#viewWill/DidLoad/Unload methods that were missing them.

Also, viewWillLoad methods removed.  They're not part of the API, and never called.
Pulsating Scene clearColor

Scenes now pulsate their clearing colors between light and dark gray at a 2-second interval.  This is an inexpensive way to more easily see if areas of the screen are not being drawn on (the point of the clearing color, really).  And it looks a little retro-tech.

Note: The exact same lines of code were added to both SceneForGLK and SceneForCG, so no DRY.  These should be merged into the superclass (or ideally, other classes), now that they're so similar.
SceneView exclusiveTouch YES PLEASE

I had this in an old temp commit.  We don't really need touch events getting past the SceneView (since its owning controller should be taking care of these events), so this isn't bad to have on.

Note: This is another instance of a poorly-named UIKit property.  The documentation says it's “a Boolean value that indicates whether the receiver handles touch events exclusively”, which matches the name.  However, that's not what it does— overlapping views (such as the OptionsDrawerView's handle, even with its exclusiveTouch turned off) still get events first and foremost.  So I guess it just ensures events will go no further than the given view and controller, even if the touch event handling methods aren't implemented or call super, are using other wizardry such as UIGestureRecognizer.