[ios][core][tools] fix expo go versioning issues on ios (#23012)

# Why

fix expo-go ios versioning for sdk 49
close ENG-8955

# How

- a lot of mess transform rules update mainly for react-na

[ios][core][tools] fix expo go versioning issues on ios (#23012)

# Why

fix expo-go ios versioning for sdk 49
close ENG-8955

# How

- a lot of mess transform rules update mainly for react-native 0.72 and reanimated v3
- [core] rename `ExpoRuntime -> EXRuntime` in objc for versioning
- [updates] force casting for the `UpdatesConfig` (i'll leave comment for this)
- [react-native-lab] add correct dependencies to make versioned code build passed

# Test Plan

`et add-sdk -p ios -s 49.0.0` + ios versioned expo-go + sdk49 ncl

show more ...

[go] add network inspector support (#22741)

# Why

add network inspector support for expo go
close ENG-8010

# How

integrate the ExpoRequestCdpInterceptor from expo-modules-core. unlike expo

[go] add network inspector support (#22741)

# Why

add network inspector support for expo go
close ENG-8010

# How

integrate the ExpoRequestCdpInterceptor from expo-modules-core. unlike expo-dev-launcher to use hacky solution, we want to enable the network inspector on release mode, so the implementation follows formal way.
- on ios, we leverage the `RCTSetCustomNSURLSessionConfigurationProvider` from react-native to create dedicated `URLSessionConfiguration`.
- on android, we already have a dedicated okhttp client from expo go. this pr just adds the interceptors.
- found image requests are not intercepted, it is because we don't use okhttp for fresco image pipeline. this pr tries to use the okhttp for fresco as react-native.
- android expo go has multiple react instances. however, the network inspector currently only support single inspector target to metro-inspector-proxy. as the result, we only limit the current foreground activity to send network inspector events.

# Test Plan

ncl + expo go to test the network inspector

show more ...