Fix location of intersect point for @turf/point-on-line.

[dpmcmlxxvi]

This addresses #691 and #722. A few issues to point out:

• The location property of the intersectPt was being computed using the closestPt which was initialized to Infinity which yielded spurious results. I believe it should be computed using intersectPt.
• I think the current implementation was passing its tests because the expected fixture values were using the values from the algorithm itself. For example, the test turf-point-on-line - points on top of line uses a line with length 0.30576 and places 10 equally spaced points on it. So the first point should have been at 0.030576 but the test was expecting it at 0.021111. Hence the fixtures have been updated accordingly.

I checked the results and #691 and #722 appear to have been fixed. Could use a double check though.

---

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Have read How To Contribute.
• Run npm test at the sub modules where changes have occurred.
• Run npm run lint to ensure code style at the turf module level.

[DenisCarriere]

Thanks, this change makes sense, no more NaN

[DenisCarriere]

Looks good!