chore: upgrade demo projects and align dependencies

[velocitysystems]

chore: Upgrade demo projects and align dependencies

Description 📝

• Purpose: The ExpoDemo app was on Expo SDK 52 with outdated dependencies that no longer built successfully. This PR upgrades it to Expo SDK 55, aligns shared dependencies with the Demo app, and cleans up generated native folders from git tracking.
• Approach: Upgraded Expo SDK and all related packages to SDK 55, configured Metro to support local SDK development via symlink, and gitignored the generated android/ and ios/ folders since they are regenerated by expo prebuild.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Updates

👉 Upgraded ExpoDemo from Expo SDK 52 to SDK 55 (React Native 0.83.2, React 19.2.0)
👉 Aligned shared dependencies (@react-navigation/*, typescript, @types/react) with the Demo app
👉 Added metro.config.js to support local SDK development via file:../sdk symlink (watchFolders, blockList, extraNodeModules)
👉 Gitignored generated android/ and ios/ folders — regenerated by expo prebuild
👉 Fixed Kotlin version mismatch in Android build (pinned kotlin-gradle-plugin to 2.1.20)

Screenshots 📷

N/A — internal tooling/demo app changes

Test plan 🧪

• Run npx expo run:ios in ExpoDemo — verify app builds and launches on iOS simulator
• Run npx expo run:android in ExpoDemo — verify app builds and launches on Android emulator
• Verify Raygun crash reporting works on both platforms
• Verify RUM events are sent on both platforms
• Run npx expo prebuild --clean and rebuild — verify native folders regenerate correctly
• Verify Demo app still builds and runs on both platforms

Author to check 👓

• Project and all contained modules builds successfully
• Self-/dev-tested
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)

Reviewer to check ✔️

• Project and all contained modules builds successfully
• Change has been dev-/reviewer-tested, where possible
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)