Handle textInput events in EditorComponent instead of on InputComponent

This commit also changes input handling to be more like it was in the
previous editor. We're using textInput rather than input events because
they are emitted *before* characters are inserted, enabling much simpler
detection of characters inserted via the accented-character menu on
OS X.

Previously I avoided this because something about it was causing reflows
in the old editor, but in this editor that doesn't seem to be a problem,
and it's actually faster.
Don't call preventDefault for spaces to prevent browser scrolling
Add editor component resize spec
Add the simplest resize fix that will work.
Move scroll view measurements to componentWillUpdate
Don't perform an update in response scroll view dimension changes

We always measure the scroll view in the ::componentWillUpdate hook, so
performing *another* update in response to the measurement causes an
invariant violation in react. Whenever we are measuring, we are always
already updating.
added delete to end of line
Ignore plist tests/
Ignore build/Release/obj directory
Don't include *.pdb files
deleting only selection if selection is not empty
Escape ignored patterns
:lipstick:
:lipstick: Use string interpolation
Merge pull request #2629 from atom/ks-smaller-windows-build

Smaller Windows build
Upgrade to language-yaml@0.7
Use ::getMarker for fold decorations instead of new DisplayBufferMarker
Add startScreenRow and endScreenRow to DisplayBuffer::findMarkers
Add containedInScreenRange to DisplayBuffer::findMarkers
Add intersection support to DisplayBuffer::findMarkers