feat: DrawerLayoutIos

[Gregoirevda]

Summary:

Adding equivalent of existing DrawerLayoutAndroid.
I'm using the method added in PR #37873 for AppDelegate too only contain enhancements.
Native Drawer, with gestures and button to open and close.
It does have issues:

• Can't make flex-1 work within DrawerLayoutIos children. DrawerLayoutIos needs to have a specific width and height. Can't bound it to the drawer full size.
• Children of DrawerLayoutIos are correctly rendered and updated in the drawer, but they are also rendered within the current tree

Changelog:

Pick one each for the category and type tags:

[IOS] [ADDED] - Adding LayoutDrawerIos

Test Plan:

Tested on simulator iPad Pro iOS 16.2

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	9,044,767	-512
android	hermes	armeabi-v7a	8,294,048	-498
android	hermes	x86	9,560,950	-512
android	hermes	x86_64	9,403,301	-502
android	jsc	arm64-v8a	9,603,752	-779
android	jsc	armeabi-v7a	8,730,474	-769
android	jsc	x86	9,690,805	-766
android	jsc	x86_64	9,937,143	-769

Base commit: 637ffb1
Branch: main

[Gregoirevda]

To the reviewer, this is definitely WIP. I think we should have DrawerLayoutIos props aligned with DrawerLayoutAndroid and have the native code in Libraries instead of template. Which isn't too much work. I would like to get a sense of the feasibility to have this component added in RN first.

How can I easily edit Library instead and have it running locally in template or another app?

[Pranav-yadav]

Just for ref: this is re-land of #37924

[Pranav-yadav]

@cortinico can you ping someone to review this?

[Gregoirevda]

@Pranav-yadav I started the refactor yesterday evening. I'm updating react views instead of the template and using the drawer in rn-tester app as it should be done. I'll also align the interface between both; especially the renderDrawer prop.

There will be a new prop introduced 'visible' which would be responsible from Js to have the drawer view setup (open and close methods still responsible for showing it). As currently DrawerLayoutAndroid doesn't work with react navigation because a view doesn't unmount when navigating away. Fixes #37495
This is working great on iOS too

[Pranav-yadav]

Sure. That seems great.
Let us know whenever this PR is ready for the review :)

[github-actions]

• ⚠️ packages/rn-tester/js/examples/DrawerLayoutIos/DrawerLayoutIosExample.js line 19 – Empty components are self-closing (react/self-closing-comp)

[javache]

Why should this component go in React Native core? Would it be better served as a community package?

We have DrawerLayoutAndroid because it's a core Android SDK component, but it would be better if these weren't part of React Native's core.

[cortinico]

See @javache comment. We're looking into making the core smaller, and we don't want to add other components like this one. Is there a strong argument to have this oen included?