refactor: use core Node.js resolve function if possible

[watson]

I'm actually a little unsure about if this actually works 100% as expected. But if it does, I think this is a good improvement. See browserify/resolve#188 for details.

So I'm a bit hesitant to merge this until we know for sure.

[Qard]

Seems reasonable, as far as I can tell.

[timfish]

Can we revisit this PR?

We've got reports that this impacts performance by around 30%

• @sentry/node slows server start times significantly getsentry/sentry-javascript#15034

[watson]

This was never merged because I never put in the time to get confident in it not breaking under certain circumstances (as mentioned in the PR description). I think my main concern was the feature detection logic. I see two roads forward right now:

1. We ship it as is
2. We bump the min required Node.js version to 8.9.0 or later, in which case we don't need to feature detection logic and can just use the Node.js core function

[timfish]

It looks like this PR fails the tests for Node 8, 10, 12 and 14 but they pass for Node 16 onwards.

I'll try and work out why!