feat(iOS): early TurboModule discovery

[tjzel]

Summary:

At the moment user-made TurboModules are discovered during the evaluation of the script - conversely to Android, where it happens before this evaluation. Because of that it's impossible to instantiate a module that we don't know the name of pre-bundle.

To implement this I used modulesProvider codegen config field to get the names of the TurboModules and initialize their holders early.

Changelog:

[IOS] [ADDED] - Added ability to discover TurboModules pre-bundle.

Test Plan:

Before	After

[cipolleschi]

Thanks for the PR. I left a few comments that has to be addressed.
This feature might also create some performance issues, delaying the app startup.
It would be great if you can wrap the _discoverModules in a featureFlag check, so we can disable it if we have a regression in the startup performance.

Feature flags for React Native are documented here

[cipolleschi]

this is a breaking change. every implementer of the delegate will have to implement this.
It is better to move this to be optional and to handle the optionality.

Also, the documentation is missing.

[tjzel]

I didn't know there is an application for multiple delegate implementers. I'll make it optional as you suggest and add relevant documentation.

[tjzel]

Done in e3db6d5.

[cipolleschi]

please, make the method in the delegate @optional, and handle this here like:

if ([_delegate respondsToSelector:@selector(getModuleNames)]) {
  ...
}

[tjzel]

Done in e3db6d5.

[cipolleschi]

we should check whether the delegate implements this method or not.

[tjzel]

Done in e3db6d5.

[cipolleschi]

we should check whether the dependencyProvider implement this method.
People could, in principle, create custom dependency providers

[tjzel]

Done in e3db6d5.

[react-native-bot]

	Warnings
⚠️	❗ JavaScript API change detected - This PR commits an update to ReactNativeApi.d.ts, indicating a change to React Native's public JavaScript API. Please include a clear changelog message. This change will be subject to extra review. This change was flagged as: BREAKING

Generated by 🚫 dangerJS against e3db6d5

[tjzel]

Thanks for the review! I tested the changes flipping the feature flag on and off and it worked as expected.

[RSNara]

@tjzel, could you elaborate on the motivation behind this change? Why do we need the module holders initialized early?

[tjzel]

@RSNara I talked about it in this comment #53282 (comment), early module holder initialization was for the purpose of finding modules conforming to a certain protocol.

[tjzel]

Closing in favor of #53928