[Bug]: React Native navigators ignore nested RouteView children and Outlet

### Package

@effector/router-react-native

### What happened?

The navigator configuration accepts RouteView objects from @effector/router-react, and RouteView supports nested children for Outlet rendering. However, both navigators pass routeView.view directly to Stack.Screen or Tab.Screen without providing the OutletContext or rendering routeView.children.

A parent RouteView with an active nested child therefore renders without its child content in React Native.

### Reproduction

1. Create a parent RouteView with children containing a child RouteView.
2. Render Outlet from the parent view.
3. Register the parent view in createStackNavigator or createBottomTabsNavigator.
4. Open the child route.

Expected: Outlet renders the active nested child view, matching createRoutesView behavior.
Actual: the navigator bypasses createRoutesView and Outlet receives no nested RouteView context, so the child view is not rendered.

### Environment

- @effector/router-react-native: 1.0.1
- @effector/router-react: 1.0.1
- @effector/router: 1.1.1
- effector: >=23
- React: 18 or 19
- React Native: >=0.70
- Node.js: 24.x

### Logs / screenshots

Not applicable; this is a deterministic nested RouteView contract issue.

Start at the createStackNavigator and createBottomTabsNavigator entry points in @effector/router-react-native, then compare their RouteView handling with createRoutesView in @effector/router-react. Reproduce a parent RouteView with a nested child and an Outlet. Done means both React Native navigators provide the nested RouteView context so Outlet renders the active child view.

Written by the indexing model from the issue text.