Set x-matched-path fixing dynamic routing

[hanford]

This PR ensures x-matched-path is set, so Next.js#handleRequest is able to recognize and render dynamic routes.

It appears Next.js uses this header pretty extensively in it's base-server, to determine whether or not we're in an edge runtime. Without this header, Next.js doesn't match the URL segments resulting in a "Internal Server Error" page.

I'm happy to change any part of this PR, but think this might be one of the "cleaner" solutions I've been able to come up with.

---

I've also created a reproduction of this bug, along with a patched version of next-on-pages that proves that this solution works over here: https://github.com/hanford/next-on-pages-32

closes #32

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1b20511

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[hanford]

Hmmmm.. going to close this until I can get it working 100%