chore(e2e): add Expo example app setup and E2E test support

[floydkim]

Summary

• Added a dedicated setup-expo-example-app script for Expo example app provisioning.
• Extended npm run e2e to support Expo apps via --framework expo.
• Unified app identifier format to com.codepush.<app> across RN CLI and Expo flows.
• Added EN/KO docs for Expo setup and E2E usage.
• Added scripts-level type checking and removed unused legacy bundle-hash scripts.
• Updated example app generated artifacts (RN0840) as part of E2E/setup changes.

Changes

• New Expo setup CLI:
  • Requires --sdk <version>
  • Optional --beta, --project-name, --ios-min-version
  • App naming: Expo{sdk} / Expo{sdk}Beta
• Expo setup automation now:
  • Configures CodePush plugin in app.json
  • Sets iOS/Android identifiers with com.codepush.<app>
  • Adds local release scripts (expo run:* with release mode and --no-bundler)
  • Runs prebuild for native projects
  • Handles Expo prerelease dependency resolution (--legacy-peer-deps)
  • Wires Expo Router home route to render App.tsx for test consistency
• E2E runner enhancements:
  • Added --framework expo
  • Expo release now uses -f expo and node_modules/expo-router/entry.js
  • RN release entry auto-detects index.js / index.ts
  • App ID resolution improved to read Expo identifiers from app.json first (with Android gradle fallback)

Motivation

• Separate Expo setup concerns from RN CLI setup flow.
• Support stable and prerelease Expo SDK scenarios with reproducible setup.
• Run E2E consistently for both RN CLI and Expo projects with one runner.