Replace source-map with @jridgewell/trace-mapping

[SimenB]

According to its benchmarks, it's way quicker, and it doesn't require us to use async code. Main motivation however, is that 0.7 of source-map is completely broken on the upcoming node v18: nodejs/node#42638

I tried a quick migration, but v8-to-istanbul uses consumer.generatedPositionFor, which doesn't exist in @jridgewell/trace-mapping.

/cc @jridgewell

[jridgewell]

I currently only track from generated -> original positions. I think I can add a lazy initialize for original -> generated position without affecting, which should still be fast. Although, you're only usage of generatedPositionFor is just to get the position of the next segment range. I could easily expose that as a method, which would be considerably faster.

[SimenB]

If it can be done in a better way, that's of course preferable 😀 I doubt @bcoe is particularly bound to the current implementation

[jridgewell]

Turns out there's not a faster algorithm that we can do. I misunderstood the API you were trying to implement, and in order to find the start of the next segment in source order, you need to use generatedPositionFor. It's now implemented. I'll do a release later today or Mon

[SimenB]

Sweet, thanks!