Increase window location check specificity for Expo 53+

[erquhart]

Fixes #206, #214

Expo runtime introduced a default polyfill to metro runtime, making window.location no longer undefined. This breaks some of our client checks for the RN environment.

This fix makes checks more specific and looks for the actual property we're interacting with to be undefined.

#207 addresses this by adding an explicit prop, which definitely works, but I'd like to avoid adding more props. The library should just handle this for users.

A patch in #206 used navigator.product as a reference, which does appear to be reliably set to ReactNative (source). This is an option for the future if more changes in platforms make checking location object properties a dubious practice.
Not an option, turns out navigator.product is deprecated 🙃

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
convex-auth-docs	✅ Ready (Inspect)	Visit Preview	May 15, 2025 1:46pm

[thomasballinger]

If there's an expo-endorsed way to detect the environment even better, but let's do this

[erquhart]

The Expo way is the RN way, which is to import Platform from react-native. They don't have a blessed way (that I'm aware of) for cross platform libraries that don't directly use the react native package.