Re.pack and its Module Federation / Micro-frontends is not working with expo

### Description

I'm building a multi-tenant React Native platform using Expo, where different customers can have different feature sets.

The ideal architecture would allow downloading or loading feature modules at runtime (similar to Module Federation / Micro Frontends) without rebuilding the entire application.

After reading the documentation, I noticed that Re.Pack currently doesn't officially support Expo.

Official support (or an experimental guide) for integrating Re.Pack with modern Expo projects using:

- Expo SDK 53/54+
- Expo Router
- Expo Development Builds (not Expo Go)
- Android & iOS
- React Native New Architecture

Even if Expo Go cannot be supported due to Metro, it would be extremely valuable if Re.Pack could work with custom development builds and production Expo applications.

## Use case

- One host application serves multiple tenants.
- Some features should be downloaded or enabled independently.
- We'd like to avoid publishing a new application whenever a new module is introduced.

Module Federation seems like an ideal solution for this use case.

## Questions

1. Is Expo support on the roadmap?
2. Is there any technical limitation preventing Re.Pack from working with Expo Development Builds?
3. Has anyone successfully integrated Re.Pack with Expo Router?
4. Are there any recommended alternatives for achieving runtime module loading in Expo?

## Additional context

The current documentation states:

> "Officially, Re.Pack doesn't support Expo."

However, since Expo now supports custom development builds and prebuild workflows, it seems that supporting Expo (outside Expo Go) could unlock many enterprise use cases.

I'd appreciate any guidance on whether this is feasible.

No files, tests, or code entry points are named. Start by reviewing the documented statement that Expo is unsupported and assess the requested scope: Expo SDK 53/54+, Expo Router, development builds, Android and iOS, and the New Architecture; done would be an official support path or experimental guide with the stated limitations explained.

Scritto dal modello di indicizzazione a partire dal testo della issue.