fix(sveltekit): Termporarily disable serverside load tracing

[Lms24]

We discovered that our serverside handleLoadWithSentry wrapper caused two distinct transactions being created on page loads - one for the page load request and one for the load function (if one exists for that page). This shouldn't happen. We need to investigate how to fix this.

As a short-term solution, we disable tracing on the serverside load wrapper to avoid quota usage increase for our users.

Note: I basically removed the trace call and added back the error reporting logic. However, I adjusted types to accept ServerLoad and Load functions as discovered in #7581

ref #7526

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	20.57 KB (+0.01% 🔺)
@sentry/browser - ES5 CDN Bundle (minified)	64.2 KB (+0.02% 🔺)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	19.13 KB (+0.02% 🔺)
@sentry/browser - ES6 CDN Bundle (minified)	56.58 KB (+0.02% 🔺)
@sentry/browser - Webpack (gzipped + minified)	21.59 KB (+0.02% 🔺)
@sentry/browser - Webpack (minified)	71.66 KB (+0.02% 🔺)
@sentry/react - Webpack (gzipped + minified)	21.61 KB (+0.01% 🔺)
@sentry/nextjs Client - Webpack (gzipped + minified)	51.87 KB (+0.04% 🔺)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	27.92 KB (+0.08% 🔺)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	26.09 KB (+0.07% 🔺)
@sentry/replay ES6 CDN Bundle (gzipped + minified)	44.33 KB (+0.08% 🔺)
@sentry/replay - Webpack (gzipped + minified)	38.39 KB (+0.09% 🔺)
@sentry/browser + @sentry/tracing + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	62.53 KB (+0.08% 🔺)
@sentry/browser + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	56.06 KB (+0.06% 🔺)