Fix Expo Go check (#13036)

StoreClient means it _is_ Expo Go, so this predicate was doing the
opposite of what it intended.

Regardless, there's a more obvious check if the app is running in Expo
Go, and it's what is recommended by the Expo docs:
https://docs.expo.dev/guides/using-sentry/#initialize-sentry

Author: lindboe

docs/platforms/react-native/tracing/instrumentation/expo-router.mdx

@@ -13,11 +13,11 @@ The code snippet below shows how to initialize the instrumentation.
 ```javascript {6-8, 15-16, 20-25} {filename: app/_layout.tsx}
 import React from 'react';
 import { Slot, useNavigationContainerRef } from 'expo-router';
-import Constants, { ExecutionEnvironment } from 'expo-constants';
+import { isRunningInExpoGo } from 'expo';
 import * as Sentry from '@sentry/react-native';
 
 const navigationIntegration = Sentry.reactNavigationIntegration({
-  enableTimeToInitialDisplay: Constants.executionEnvironment === ExecutionEnvironment.StoreClient, // Only in native builds, not in Expo Go.
+  enableTimeToInitialDisplay: !isRunningInExpoGo(),
 });
 
 Sentry.init({
@@ -28,7 +28,7 @@ Sentry.init({
   // https://docs.sentry.io/platforms/javascript/configuration/options/#traces-sample-rate
   tracesSampleRate: 1.0,
   integrations: [navigationIntegration],
-  enableNativeFramesTracking: Constants.executionEnvironment === ExecutionEnvironment.StoreClient, // Only in native builds, not in Expo Go.
+  enableNativeFramesTracking: !isRunningInExpoGo(),
 });
 
 function RootLayout() {