[✨] `logError` prevents proper Sentry error capturing

[jessezhang91]

Is your feature request related to a problem?

I have hooked up Sentry alert monitoring on top of my Qwik app. As part of that, I needed to use their CaptureConsole integration because of the logError implementation here: https://github.com/BuilderIO/qwik/blob/70880b71995361202ae0b4725454cb2bd008ab2d/packages/qwik/src/core/util/log.ts#L10-L16

Because of this, I can't pass the raw error to Sentry and we can't get niceties like stack trace remapping via sourcemap.

Describe the solution you'd like

I would like a configuration for production builds to either tap into logError (e.g. a callback) or for production builds to just re-throw errors in logError (which Sentry will catch).

Describe alternatives you've considered

n/a

Additional context

No response