ref(core): Log normalizeDepth when normalization is skipped

[lobsterkatie]

Continuing debugging of #2809. In the most recent example event there, it's clear from the stringifying error's stacktrace that the event is hitting BaseClient._processEvent, and we can tell from the line number in that stack trace that it's getting past _prepareEvent, which is what calls normalize.

In _prepareEvent, the only way for normalization not to run is if the normalizeDepth option either isn't a number or is set to a value <= 0. (It's got a default value, so it not being set directly by the user isn't the issue.)

sentry-javascript/packages/core/src/baseclient.ts

Lines 377 to 379 in b46674c

	if (typeof normalizeDepth === 'number' && normalizeDepth > 0) {
	return this._normalizeEvent(evt, normalizeDepth);
	}

In order to better diagnose what the problem might be, this PR adds logging of the normalizeDepth value in cases where an event fails to be normalized when it should.

[github-actions]

size-limit report

Path	Base Size (b46674c)	Current Size	Change
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	19.65 KB	19.68 KB	+0.16% 🔺
@sentry/browser - ES5 CDN Bundle (minified)	63 KB	63.17 KB	+0.28% 🔺
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	18.32 KB	18.35 KB	+0.18% 🔺
@sentry/browser - ES6 CDN Bundle (minified)	56.15 KB	56.35 KB	+0.36% 🔺
@sentry/browser - Webpack (gzipped + minified)	22.1 KB	22.13 KB	+0.14% 🔺
@sentry/browser - Webpack (minified)	75.86 KB	76.07 KB	+0.27% 🔺
@sentry/react - Webpack (gzipped + minified)	22.14 KB	22.17 KB	+0.14% 🔺
@sentry/nextjs Client - Webpack (gzipped + minified)	46.26 KB	46.31 KB	+0.1% 🔺
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	27.1 KB	27.13 KB	+0.11% 🔺