Move last cue identifer tests to integration folder.
Merge pull request #65 from RickEyre/misc-moves

Move last cue identifer tests to integration folder.
Fix infinite loop bug on blank-file.vtt.

Problem was that we weren't explicitly checking size >= 0 on
streaming tests. Which means that on tests with an initial size of
0 we would keep looping indefinitely.
Fix no spaces between cue times separator bug.

The problem was that after we consume a timestamp we would replace
everything that isn't a whitespace until the next whitespace. In
situations with no white spaces this means it would remove the
rest of the cue time data. Changed so that we replace up until
the next whitespace or "-" character.
Merge pull request #66 from RickEyre/issue59

Fix infinite loop bug on blank-file.vtt. Closes #59.
Merge pull request #67 from RickEyre/issue62

Fix no spaces between cue times separator bug. Closes #62.
Fix regions without newlines to be parsed.

We need to synthesize the end of the current cue or region when
calling flush().
Merge pull request #69 from RickEyre/issue48

Fix regions without newlines to be parsed. Closes #48.
Don't trim whitespace after splitting on whitespace for settings.

- The spec doesn't say to do this.
- I've updated regions/space-before-delimiter.vtt to compare to a failing
JSON file as it should actually fail.
Use the same JSON file for good region tests.
Don't set settings if it's an empty string.

This was resulting in behaviour where we were setting settings even
when no value was correctly parsed.
Add bad-delimiter.vtt to region/id tests.

Forgot to add this into the test.js file when it was added.
Fix bug where newline before WEBVTT was being parsed.

The problem here was that we were consuming the newline on the
first call to parse and therefore on subsequent calls to parse
the parser has no idea that there was a newline there to begin
with.
Make unicode characters in JSON test files humanly readable.
Fix test harness to work with BOM files.

We were failing on testing files with BOM characters in them
as node translates the BOM character to 0xFEFF when reading
it in. Solution was to replace 0xFEFF with the correct code
point sequence and pass that to the parser.
Add snap-to-lines flag to cue settings.

The spec specifies that a snap-to-lines flag is to be set when
the line cue setting is a percentage. This is to differentiate
between whether or not line is an integer or a percentage.
Check for U+FEFF instead of UTF8 BOM sequence.

Since the parser works with a buffer that has been decoded it should
really be looking for the BOM character as an U+FEFF code point.
Merge pull request #73 from RickEyre/encode-fix

Check for U+FEFF instead of UTF8 BOM sequence.
Merge pull request #72 from RickEyre/issue15

Add snap-to-lines flag to cue settings. Closes #15.
Do not accept "-->" in region header id.