[expo-updates][android][ios] allow reloading in dev mode in store clients

[esamelson]

Why

less urgent fix than #10308 and #10309, review can wait if needed

There was a small regression with the Updates JS module API in SDK 39, namely that it is no longer possible to use reloadAsync in development mode in the store clients. This PR fixes that behavior for the store clients.

How

Add a separate canRelaunch check that the module will call, and always return true in the clients, rather than checking to see if expo-updates is being used to load the app. This works because we can always reload in the store clients even if expo-updates is not being used (e.g. in development mode).

Test Plan

Test Updates.reloadAsync() in development sandbox in both UNVERSIONED and SDK 39.

[github-actions]

	Fails
🚫	📋 Missing Changelog 🛠 Add missing entries to: packages/expo-updates/CHANGELOG.md

🛠 Suggested fixes:

📋 Missing changelog

Apply suggested changes:

diff --git a/packages/expo-updates/CHANGELOG.md b/packages/expo-updates/CHANGELOG.md
index 70a21894..17f6010f 100644
--- a/packages/expo-updates/CHANGELOG.md
+++ b/packages/expo-updates/CHANGELOG.md
@@ -8,6 +8,8 @@
 
 ### 🐛 Bug fixes
 
+- allow reloading in dev mode in store clients. ([#10310](https://github.com/expo/expo/pull/10310) by [@esamelson](https://github.com/esamelson))
+
 ## 0.3.4 — 2020-09-22
 
 ### 🐛 Bug fixes

Generated by 🚫 dangerJS against 985ac80

[github-actions]

Native Component List for this branch is ready

[ide]

We'll need to cherry-pick this back and remember to rebuild the SDK 39 AAR.

[esamelson]

no need to rebuild the AAR as versioned expoview code is built from source, and this PR already backports the necessary changes. will land now and cherry-pick to sdk-39

[brentvatne]

#10464 (comment)

[Nantris]

@brentvatne we're still seeing Updates.reloadAsync() failing in development, saying it's not supported in development.

We're running SDK 39 and using 39.0.3.tar.gz. Is there something I'm overlooking?

[brentvatne]

@slapbox - probably you don't have expo-updates@0.3.5 in your project

[Nantris]

@brentvatne you're right! Thank you, much appreciated!

Quick follow-up, is there a place we can consult for dependency versions?

We reference the bundledNativeModules.json for dependency versions by SDK version due to an issue with yarn/expo/monorepos where we can't use expo install [some package] - but those can become out of date once the SDK starts getting patches I see.

[brentvatne]

@slapbox - it's actually not out of date because it specifies a version range. we don't update it every time we release a patch version bump because we'd have too many releases of the expo package if we did that. if you ran yarn upgrade then ~0.3.3 would end up being updated to ~0.3.5

[Nantris]

Ah good call. We usually just run yarn, not yarn upgrade. Thanks again.