Fix test fixture for the multi range example

[honzajavorek]

Context is explained in #348. The example used for testing multiple-ranged souce maps for annotation stopped to produce multiple ranges after Drafter 4.0.1 has been released and propagated through vaguely pinned transitive dependencies.

I've used a trick from this API Blueprint suggested by @kylef, which serves for producing multiple ranges in the Drafter's test suite.

The test verifies that code normalizes the range to boundary positions:

assert.deepPropertyVal(annotation, 'location', [[7, 5], [13, 19]]);

The ones I hardcoded to the test are verified manually through VS Code. On the screenshots below you can see how my cursor position translates to line and column numbers in VS Code's blue bottom bar:

[kylef]

Makes sense, although I wonder if/when this will break in the future. Not sure what other cases can cause multi-line source maps (under cases where there is indentation).

[honzajavorek]

I guess this is all we have if we want to test against fixtures. I didn't check, but I believe there are also unit tests. If you wipe all real cases out of the parse results, we can rely at least on those.