fix: normalize injected import paths on windows

[james-elicx]

This PR does the following:

• Normalizes the import paths that get injected on Windows machines.

This should hopefully resolve the following issue that I believe is caused by backslashes in Windows path names:

[X [ERROR] Could not resolve "......__next-on-pages-dist__webpackee2d6a0d46f7afe4402d9e841f4a3be3.js"

    <stdin>:1:124:
      1 │ ...838 } from '..\..\..\__next-on-pages-dist__\webpack\ee2d6a0d46f7...
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  You can mark the path "......__next-on-pages-dist__webpackee2d6a0d46f7afe4402d9e841f4a3be3.js" as external to exclude it from the bundle, which will remove this error.

[changeset-bot]

🦋 Changeset detected

Latest commit: 8bdf62a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@cloudflare/next-on-pages	Patch
eslint-plugin-next-on-pages	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

🧪 Prereleases are available for testing 🧪

@cloudflare/next-on-pages

You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/5702113242/npm-package-next-on-pages-412

@cloudflare/eslint-plugin-next-on-pages

You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/5702113242/npm-package-eslint-plugin-next-on-pages-412

[DeJayDev]

As a Windows user with this issue I can confirm this prerelease fixes the issue :)

[dario-piotrowicz]

awesome! 😄👍

Thanks a lot @james-elicx 😄