inspired by #13830, but separate: it makes no sense to log a stack trace with a 404, we can just log Not found: /blah. The stack trace will only ever include SvelteKit internals, there's nothing that a developer can do with that information.

We could probably improve logging of server-side errors all round (e.g. a nicely formatted [500] GET /whatever with a sanitized stack trace, maybe a code frame if appropriate, maybe opening a model on the client, etc) but I thought it would make sense to start with this no-brainer PR

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.