[snackager] try to fix expo-linear-gradient issue

[Kudo]

Why

expo-linear-gradient@12.1.2 on sdk 48 is broken on android: expo/expo#24424
close ENG-10114

How

expo-linear-gradient 12.1.1 <-> 12.1.2 does not change anything from js side. i think the problem is coming from snackager. comparing the two bundles:

• https://d37p21p3n8r8ug.cloudfront.net/snackager-1/expo-linear-gradient@12.1.1-android/bundle.js
• https://d37p21p3n8r8ug.cloudfront.net/snackager-1/expo-linear-gradient@12.1.2-android/bundle.js
  i noticed they are slight changes, mostly ESM / CJS difference.

my hypotheses are:

• our old system.js does not support CJS
• we install latest @babel/runtime
• from @babel/runtime 7.13.0, it detects whether to use ESM/CJS by node.js
• we may update node.js in between
• when bundle is transpiled in CJS, it would be wrong.
• Probably root cause because expo-modules-core has a breaking change, we should not install expo-modules-core@* in this case.

the solution is passing exact @babel/runtime version to install. that could prevent the inconsistent version between @babel/plugin-transform-runtime and @babel/runtime.
since our @babel/runtime is 7.12.5, we could also use the explicit useESModules.
To fix the expo-modules-core breaking change, now this pr tries to fetch bundledNativeModules from api server and install recommended versions accordingly.

Test Plan

deploy staging to test the test case from https://staging-snack.expo.dev/@kudochien/linear-gradient. may wait 24 hrs for cloudfront to purge the cache.

[linear]

ENG-10114 [expo-linear-gradient][Android] Linear-gradient rendering incorrectly on Android 13

This issue was automatically imported from GitHub: expo/expo#24424

Issue accepted by brent

---

Summary:

• The user is having an issue with gradients not working on Android in the current version of Expo.
• This issue can be reproduced using the snack provided in the ExpoLinearGradient section of the Expo docs.
• The gradients seem to work as expected on iOS, but not on Android as is highlighted with the screenshots the user provided.
• The user created a minimal reproducible example available at a provided GitHub link.
• The underlying issue is not specified, so further investigation will be required to determine the cause for this unexpected behavior.