[TRACKING] Enhanced Expo support

[dannyhw]

lets use this as a place to discuss and outline the path toward better expo support

The first steps should be ensuring:

• normal repack functionality
• easy setup via cli command
• expo module/plugin to simplify setup of native dependency (script manager)
• expo features like OTA working as expected.

Following this, the nice to haves

• module federation support
• supporting metro module federation where possible
• assess if expo updates can work with repack or offer examples of alternative setups
• benchmark metro vs repack for expo projects

Please offer your thoughts or suggestions in the comments below

[whydidoo]

@dannyhw, I see this as a dedicated Re.Pack Expo plugin built on top of @module-federation/metro, preserving the standard Expo CLI, Router, Metro, and EAS Update workflows while adding Module Federation support.

[dannyhw]

@whydidoo I think thats one part of it, we could also support repack alone as a bundler so that people can make use of rspack features for example tree shaking etc.

I'm not sure if we should include metro functionality in this repo unless its somehow generic/shared code that we can provide for use with metro or repack. If we want to build metro specific things I think we could make a separate repo maybe? Unless it would be causing more work by doing so.

[whydidoo]

@dannyhw, Agree. I think this issue should focus on first-class Expo support using Re.Pack/Rspack: dev and production builds, Expo Router/Modules, a Config Plugin, CLI setup, and later OTA.
Metro-specific MF should remain separate unless we find generic runtime or asset-handling code reusable by both integrations. I suggest starting with an Expo SDK 56 fixture and minimal Config Plugin.