Create tests so internal console warnings do not make it to Sentry and count towards users error quota

[stephanie-anderson]

When you call startTransaction() without addTracingExtensions() being called, the SDK gives you a console warning that you need to call it for startTransaction() to properly work (this is so you can tree shake performance). We call startTransaction() in various integrations internally. If users do not call Sentry.init we will emit this warning because of auto instrumentation.

But if users have the CaptureConsole integration enabled, it would create events for this warning. Normally we sandbox (escape) these console messages but apparently this has slipped at some time.

[lforst]

The real task here is to check for all usages of console in the SDK and sandbox them with consoleSandbox.

[lforst]

This is not really testable. I opened a PR to ensure that all console logs in our codebase are wrapped in the console sandbox.