* Fix locEnd() for postcss parser

`node.source` doesn't have an `end`, but `node.nodes[-1].source` does.

Fixes #2267

* Add regression test for #2267

See #2295 (comment)

* Make locEnd() postcss fix more focused

This passes the tests again.

* Use getLast() instead of .slice()

See #2295 (comment)

* Move CSS range test into tests/range_css

This is so that the AST_COMPARE=1 tests don't try to parse CSS with Flow.

* Add test for #2297

* Add JSON types to isSourceElement()

See #2297

* Avoid expanding format range when possible

This fixes #2297

* Move JSON range test into tests/range_json

This is so that the AST_COMPARE=1 tests don't try to parse JSON with Flow.

* Check parser in isSourceElement()

Otherwise JSON formatting would format weird things inside of JS.
See #2298 (comment)

* Use arrow functions instead of .bind()

See #2298 (comment)

* Add test of range-formatting JSON identifier

See https://github.com/prettier/prettier/pull/2298/files#r124410750

* Allow range-formatting JSON identifier

See https://github.com/prettier/prettier/pull/2298/files#r124410750

* Fix lint

The tokens are attached to the location via the prototype (so they are not visible when you JSON.stringify) but the various places where we traverse the ast see them. It causes stack overflows and comments that are not printed because they are attached to tokens instead of real nodes.

Fixes #2302

"Daniel Schafer: Yeah, that's definitely what I'd describe as the canonical style; anytime you have two "things" on a line, use commas, but if you have a newline it's not needed."

It appears in some files inside of fb codebase

I couldn't figure out what the separator was, I tried `,`, `on` but none of them worked. Turns out it is `|`!