Add naming strategy option for XCFrameworks

[kraenhansen]

Add an option to choose a naming strategy of XCFrameworks as they're vendored (i.e. copied and renamed) into the host package.

You can choose between two modes:

• "hash": Will traverse the filesystem upwards from the Node-API xcframework directory and use the package name of the encapsulating package. This package name is then appended with the relative path to the xcframework and this combined path (package name + relative path) is then hashed and truncated. The advantage is that we have no restrictions on how many Node-API modules a dependency of an app can bring and we can even disambiguate between Node-API modules of the same name within a single package. The disadvantage is that the name of the framework is not easily translatable to the original Node-API module, which might make it harder to debug issues. (We could provide tools to scan and resolve the original file from the hash though 🤔)
• "package-name": Will traverse the filesystem upwards from the Node-API xcframework directory and use the package name of the encapsulating package. The advantage being that names don't collide across dependencies of an app and the frameworks in Xcode and crashdumps will make more sense. The disadvantage is that each dependency of an app can bring at most one Node-API module.

The option defaults to package-name as I believe that strikes the right balance between DX and compatibility with the existing ecosystem og packages shipping Node-API modules (of which the vast majority ships only one per package).

You can opt-into the "hash" strategy if you need to, by running pod install with an enviroment variable:

NODE_API_MODULES_NAMING=hash npm run pod-install

and setting the naming option on the Babel plugin:

https://github.com/callstackincubator/react-native-node-api-modules/blob/9254501866f58510efe9c2e202d7feeeb2071ddf/apps/test-app/babel.config.js#L3

What it looks like

With the examples sub-packages renamed to example-${counter}, this is what it looks like to a dev:

Frameworks in Xcode

Frameworks on disk

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8a4bf7b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[teodorciuraru]

Only one reviewer per PR, or is it playing with me? 😂

I'll leave comments separately, no worries.

[kraenhansen]

Only one reviewer per PR, or is it playing with me?

No - you're right. I've changed it to you - it's first come first serve 😆
I believe it's because the repo is private - other features are limited by that too.

[teodorciuraru]

Need more time on this one. Feel free to merge if needed.

[kraenhansen]

Could probably be deleted, but I'll let it stick around here for a bit longer in case it comes in handy 🙈

[kraenhansen]

I'll take what I can get 😉 I plan to merge this EOD. I have the Android support based on this and I'd like to refactor the CLI to have a single "xcframeworks" command with sub-commands, like "list", "copy", etc. I'd also like to get started on setting up CI to build and test all of this 🙏