Upgrade to SDK 46

[keith-kurak]

What

• Updated all examples to SDK 46
• Checked for removed libraries in examples per release blog (none found)
• Added a quick-and-dirty upgrade-dependencies.sh script that runs expo upgrade on all projects at once and writes the command output to a non-committed folder for review (can also run expo doctor --fix-dependencies on all projects, for those times where the SDK's RN version is updated mid-PR 😄 ).
• Spot-checked several projects based on a) if they failed to automatically update via the aforementioned script, b) were mentioned specifically during the previous update (SDK45 #371), or c) otherwise seemed interesting or notable.
• In some cases, updated additional dependencies and/ or readme's to reflect my experiences getting the spot-checked examples up-and-running
• Made readme's consistently refer to expo start across the board due to several package.json files containing no scripts.
• Remove references to global CLI and eject.

Spot-checking results

✅ with-yarn-workspaces

• updated to match the instructions in the Expo Monorepos Guide
• tweaked the npm scripts to account for removal of expo-yarn-workspaces, added separate script for watching packages (previously ran automatically after running yarn)

✅ with-electron

• I've tried adding electron at least three times in recent months, and it never works unless I run yarn expo-electron customize and add contextIsolation: false to index.js, so updated accordingly. Wondering if this should either be reflected in docs or if @expo/electron-adapter can be/ should be updated to do this by default.

✅ with-gatsby

• Kept gatsby version at 2.x, as plugin isn't compatible with 3 or 4.

✅ with-three / with-react-three-fiber

• This basic example works with Expo packages that are more recent than the peer deps specify in expo-three, plus a post 0.127.0 version of three, which fixes [Unhandled promise rejection: TypeError: null is not an object (evaluating 'gl.canvas.width')] expo-three#202

⚠️ with-splash-screen

• Works on Android, but Updates.reloadAsync() fails silently with "You cannot reload when expo-updates is not enabled" on iOS on Expo Go (not a problem with example, issue opened)

⚠️ with-nextjs

• Works if I leave @expo/next-adapter/ nextjs dependencies on the same version; homepage url hangs indefinitely if I run yarn expo-next from scratch on latest adapter version (which installs next 12.x, which uses requires webpack 5, while the adapter uses 4), I get a fatal babel error if I install the required peer-dependency version of next (^11, which can use Webpack 4, but doesn't by default).

✅ with-moti

✅ with-typescript

✅ with-tab-navigation

✅ with-drawer-navigation

• Required Babel config change due to open issue with Reanimated: Export namespace should be first transformed by @babel/plugin-proposal-export-namespace-from on export * as default from './Animated'; software-mansion/react-native-reanimated#3410

[EvanBacon]

Doesn't matter but we inject the start script when the user bootstraps with CRNA.

[keith-kurak]

good to know! Some examples were one way, some the other, so was trying to pick one and apply it across the board. Knowing that it's always there, makes sense change it to yarn/ npm, which seems more consistent with other tool's templates.