feat: if code frame error is on a single line, highlight the whole path

[SimenB]

Q	A
Fixed Issues?
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?	👍
Tests Added + Pass?	No
Documentation PR Link
Any Dependency Changes?	No
License	MIT

Before:

After:

buildCodeFrameError doesn't seem to have any tests, at least not any I could find. Thoughts on where I can add one (if you want this)

This might make sense as an option passed to path.buildCodeFrameError rather than buildCodeFrameError forcing it on consumers?

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/11362/

[JLHwung]

The highlighted path may contain many subpaths even though they are within the same line, i.e.

foo(a, b(f, { g: h(i) }))

If the whole callExpression foo(a, b(f, { g: h(i) })) is highlighted, user may even get more confused than we simply highlight the start foo.

[nicolo-ribaudo]

I prefer this PR to the current behavior. In @JLHwung example, if the problem is the whole call expression I don't see why it shouldn't be highlighted.