misc: Move to monorepo structure and Yarn V3

[krystofwoldrich]

📢 Type of change

• Refactoring

📜 Description

This PR change the repository structure to use monorepo setup.

The new structure:

• / -> monorepo root private package
• /samples -> sampel application, expo, rn...
• /packages -> RN SDK packages
• /dev-packages -> dev packages, ts-3.8 test runner, e2e tests components and runner
• /performance-tests -> applications used for measuring performance in CI

This PR updates the repository to use Yarn V3, as with Yarn V1 the sample applications would not run due to dependencies conflicts. And the original nohoist would not fix the issue. With nmHoistingLimits: workspaces the RN and Expo application are working correctly.

💚 How did you test it?

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
• All tests passing
• No breaking changes

🔮 Next steps

• Test the publish of @sentry/react-native does introduce unexpected (no) changes compared to version 6.0.0-alpha.0
• Verify version gets correctly bumped in all dependencies

#skip-changelog

This is a internal change the SDK package published should be unchanged.

[github-actions]

Android (new) Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	401.98 ms	445.34 ms	43.36 ms
Size	7.15 MiB	8.33 MiB	1.19 MiB

[github-actions]

iOS (legacy) Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	1232.49 ms	1239.14 ms	6.65 ms
Size	2.36 MiB	3.08 MiB	732.30 KiB

[github-actions]

iOS (new) Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	1239.37 ms	1236.35 ms	-3.02 ms
Size	2.92 MiB	3.64 MiB	738.25 KiB

[Lms24]

Nice work! LGTM from monorepo and publishing perspective. Noted down some things to keep in mind when we add more packages but we can do this whenever it's necessary.

Btw: We added this New SDK (package) Checklist to our monorepo docs to keep in mind what to do in which order. Some things are very JS SDK-specific but the general oder of actions and things to keep in mind should apply to this monorepo as well.

[Lms24]

l (no action required):
Are you keeping the readme of the SDK top level and you copy it to the package to get it into the tarball? No objections btw, just curious.

In the JS SDK monorepo we keep a Readme per package but I guess that's only gonna become necessary if you have more than one package.

[Lms24]

No immediate action required since you only publish one package at the moment. Once you have more than one pkg, I'd recommend to create one NPM target per package and release in package dependency order.

[github-actions]

Android (legacy) Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	448.80 ms	456.00 ms	7.20 ms
Size	17.74 MiB	20.06 MiB	2.33 MiB