breaking: replace edge option with runtime

[teemingc]

This PR removes the edge: true adapter option in favour of runtime: 'edge' | 'nodejs22.x' etc. This is what we did for the Vercel adapter previously. It makes sense to do this as the next PR will introduce route-level configs

[pkg-svelte-dev]

Install the latest version of @sveltejs/kit from 5606a03:

pnpm add https://pkg.svelte.dev/@sveltejs/kit/c/5606a03206879d63fba25d70b9c95af3b89ee6d1

Open in pkg.svelte.dev: https://pkg.svelte.dev/repos/kit/pr/17065

[changeset-bot]

🦋 Changeset detected

Latest commit: 5606a03

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

This PR includes changesets to release 1 package

Name	Type
@sveltejs/adapter-netlify	Major

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

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-kit-17065-svelte.vercel.app/

[Rich-Harris]

In two minds about this. It makes sense on Vercel because you can configure runtime and region independently (and runtime: 'edge' is deprecated anyway), but on Netlify an edge function is a categorically different beast — it's not just the fact that the code runs on Deno, it's that it runs at the nearest edge location. Given that, a boolean feels a bit more logical to me.

(Having said all that it's very unclear what 'edge location' means exactly — if it's white-labelled Deno Deploy, does that mean the 6 Deno Deploy Classic locations or the 2 Deno Deploy locations?)

[teemingc]

(Having said all that it's very unclear what 'edge location' means exactly — if it's white-labelled Deno Deploy, does that mean the 6 Deno Deploy Classic locations or the 2 Deno Deploy locations?)

Maybe @serhalp can weigh in on the specifics

rich has some concerns to resolve