fix: Windows binary location

[timfish]

It appears that path.resolve already caters for path separator differences so you can safely use forwards slashes and everything works.

Closes #1368

[kamilogorek]

Ah, nice cache, you are correct:

On Windows, both the forward slash (/) and backward slash () are accepted as path segment separator

https://nodejs.org/api/path.html#pathsep

Although I'm not sure how your original issue happened, as this code should work just fine on windows, and we never had any reports of it being broken 🤔

[timfish]

Yes, the cli was working perfectly well on Windows even with the dodgy file name.

However @sentry/nextjs does a check to see if the binary exists (ie. has been successfully downloaded) and this would not have worked on Windows because a) it was not checking for .exe b) the executable file was not where it was expected to be!

https://github.com/getsentry/sentry-javascript/blob/4b137b72e256b3773d9a8b500e857ce3ee7208a0/packages/nextjs/src/config/webpack.ts#L459-L473