hasTracingEnabled doesn't handle undefined values correctly

[nwalters512]

hasTracingEnabled doesn't handle undefined values correctly

[mydea]

Hey,

the background for this is based on browser-land, where we want to do certain things only if performance is set in any way.
We may revisit this, but for now I will fix this specifically in the node init check for performance integrations, and only load those if this is not undefined!

[mydea]

Hey,

we have updated this in the SDK, so that even if this is set to undefined, performance instrumentation will not be added by default.

(FWIW, we have not updated the hasTracingEnabled() check yet, because we need to double check to make sure there are no other effects there, but we changed this for the perf instrumentation check itself).

I will leave the issue open still because I think the fundamental problem it poses remains valid!