Fix: Add start and end propert to tokens (fixes #172)

[soda0289]

Some eslint plugins except tokens to have start and end properties
instead of range. This commit adds those properties and modifies
the tests to ignore start and end property.

[eslintbot]

LGTM

[JamesHenry]

What is the motivation behind hiding them from the tests?

PS The commit has a typo in it

[soda0289]

Well it would be a lot of work to rewrite every test. I have seen the tool we have that might help but there are still JSON tests that would need to have start and end inserted in every token node.

I looked at how espree handles this and copied the code from them.

Another way to not include them would be to add the property as non-enumerable and that way when we run JSON.stringify start and end property would not show up.

I could write a tool that could update the JSON tests and upadte the tool we have to update all the tests, not just the typescript ones.

Let me know if you think its worth it or if you think making the property non-enumerable is cleaner

[JamesHenry]

Ah yes, I had forgotten about that! I think using espree's example is more than ok 😄

Thanks so much for providing PRs for the issues you find, it's so helpful!

[JamesHenry]

LGTM, I'll fix the typo in the commit when I merge