SvelteKit redirects thrown in instrumented request handlers should not trigger captureException

[Lms24]

The incorrect behaviour seems to be present in @sentry/[email protected] - after following the setup instructions, with a pretty vanilla SvelteKit application, redirects from within the server hooks handle() function are being reported to Sentry as errors. Or rather, we see the following error since a SvelteKit redirect is not an instance of class Error:

Object.captureException
💀 Unhandled Non-Error exception captured with keys: location, status

A minimal reproduction would be something like this:

// hooks.server.ts
export const handle = async ({ event, resolve }) => {
  // dummy logic to handle users who aren't logged in
  if (event.url.pathname !== '/login') {
    throw redirect(303, '/login');
  }

  const response = await resolve(event);
  return response;
};

Originally posted by @abirtley in #7719 (comment)

[Lms24]

Hi @abirtley, thank you for reporting!

I've extracted this to a separate issue because we didn't handle this correctly in handle request handlers but only in load functions.

We should apply the same fix as in #7731 just for request handlers. I'll open a PR soon.