fix(utils): Check for performance.now() when calculating browser timing (getsentry#3657)

We should guard against performance.now not being available
when calculating browserPerformanceTimeOrigin. We do a similar check
when for our wrapper around the native performance api implementation.

Author: AbhiPrasad

packages/utils/src/time.ts

@@ -141,7 +141,7 @@ export const browserPerformanceTimeOrigin = ((): number | undefined => {
   // data as reliable if they are within a reasonable threshold of the current time.
 
   const { performance } = getGlobalObject<Window>();
-  if (!performance) {
+  if (!performance || !performance.now) {
     _browserPerformanceTimeOriginMode = 'none';
     return undefined;
   }