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.
CocoaPods usage updates

Per recommendations I'm reading and discovering:
• Removed Pods directory, and ignoring in the gitignore.
• Leaving Podfile.lock in.
• Added P-001.xcworkspace and unignored “*.xcworkspace” pattern when root-level (apparently still a bad idea when a sub-dir of an xcodeproj).

Also:
• Changed the FontAwesomeIconFactory version requirement from `'>= 1.0.1', '< 2.0'` to `'~> 1.0'` in order to avoid a CocoaPods bug.
• Updated the version of FontAwesomeIconFactory to 1.1 and CocoaPods itself to 0.20.2 in the process.
• Put basic build instructions in the README.
Merge update 'refactor/sub-GLKViewController' to branch 'master'
Minor: Made SceneViewControllerForGLK a presentation context

…since it's a container.  And that's what the iOS docs recommend.