Fix HEADER_SEARCH_PATHS for RuntimeExecutor when USE_FRAMEWORKS is enabled

[sharifhh]

Summary:

#include <ReactCommon/RuntimeExecutor.h> stopped working in react-native 0.81 when using frameworks because it is not part of ReactCommon anymore when the split happened for iOS.

to fix this I am including RuntimeExecutor in search headers same way we include ReactCommon.

Changelog:

[IOS] [FIXED] - Fix import RuntimeExecutor.h with USE_FRAMEWORKS

Test Plan:

You can enable USE_FRAMEWORKS and do #include <react/renderer/uimanager/UIManager.h> (which react-native-reanimated is doing).
Build will fail complaining that it can't find ReactCommon/RuntimeExecutor.h which is included in UIManager.h
Add my patch, it will work and build successfully

[meta-cla]

Hi @sharifhh!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[cipolleschi]

thanks for fixing this.
We should also update the install_modules_dependencies function. Can you take care of that?

[facebook-github-bot]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this in D79796637.

[sharifhh]

@cipolleschi done, I also added it to codegen template, let me do a quick run of checks to see where we do this also.

[sharifhh]

I guess that's it, no other places

[facebook-github-bot]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this in D79796637.

[sharifhh]

@cipolleschi should I do anything about tests snapshots?

[sharifhh]

I updated the tests snapshots 🙏

[facebook-github-bot]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this in D79796637.

[facebook-github-bot]

@cipolleschi merged this pull request in dacd8f2.

[react-native-bot]

This pull request was successfully merged by @sharifhh in dacd8f2

^{When will my fix make it into a release? | How to file a pick request?}

[sharifhh]

why this commit wasn't part of 81 release?
81 is not usable in current state when people use frameworks
any timeline for releasing this as a hotfix?

[cipolleschi]

because the commit landed after we cut the branch for 0.81.
To pick this commit into the release, we need to create a pick request.

I created it here: reactwg/react-native-releases#1093

0.81.1 should arrive next week, probably

[react-native-bot]

This pull request was successfully merged by @sharifhh in 4c781e4

^{When will my fix make it into a release? | How to file a pick request?}