feat: autolink native peer dependencies

[patrickkabwe]

Summary

Add opt-in support for autolinking native peer dependencies (closes #870). At the moment the CLI only autolinks packages that are listed directly in an app’s package.json, so native peers declared by a library remain invisible unless every app developer installs them manually. This change introduces a dependency.autolinkTransitiveDependencies flag that a library can set in its react-native.config.js. When enabled, the CLI reads the library’s own package.json, discovers its peer dependencies, and links any native peers that are already present in node_modules.

The approach stays entirely inside the autolinking pipeline unlike PR #2054’s --dependency-check, which mutates app dependencies so it avoids surprise installs, CI failures, and extra workflow steps. Once a library opts in, every app automatically benefits. The updates touch the config loader, schema, public types, documentation, and add loadConfigAsync test coverage.

Test Plan

yarn test packages/cli-config/src/__tests__/index-test.ts

Checklist

• Documentation is up to date.
• Follows commit message convention described in CONTRIBUTING.md.
• For functional changes, my test plan has linked these CLI changes into a local react-native checkout (instructions).

[github-actions]

There hasn't been any activity on this pull request in the past 3 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.

[patrickkabwe]

Hi @thymikee any chance for a review on this PR?

[thymikee]

Appreciate this, although it will be hard to propagate this changes, especially that expo-modules-autolinking exists and supports this use case without requiring libraries to adopt. I'd rather lean towards reusing this package if possible (might require some changes to it, but idk at the moment)