Fix: Auto linking for RN >= 0.69

[marandaneto]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

Remove the removed config from the config file.
This is a breaking change.

💡 Motivation and Context

Fixes #2267

💚 How did you test it?

Running it

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• All tests passing
• No breaking changes

🔮 Next steps

Patch https://github.com/getsentry/sentry-wizard

[marandaneto]

@bruno-garcia What if we say that the RN SDK 5.x requires RN version >= 0.69?
We could technically drop stuff like #2015
It'd be easier to maintain as well since we don't need to test stuff on older versions, we'd need to patch bug fixes on v4.x when needed though.
Ideally not the best solution for the user, but this is a breaking change and auto-linking won't work for either before or after 0.69.

[bruno-garcia]

Sounds like it's it's time. Can we spit out build warnings/errors in case the expected version doesn't match? My biggest worry is of users getting unrelated error messages, being frustrated and/or raising issues with support.

If we can break at build time, with:

Sentry 5.0 on older RN: The Sentry SDK version 5.0.0 and above requires React Native 0.69 or higher
Sentry 4.x on older RN: The Sentry SDK version 4 doesn't support React Native 0.69. Please upgrade to Sentry 5.0.0 or higher

[marandaneto]

TODO: yarn install after sentry-wizard gets released to update the yarn.lock file.

[Acetyld]

Any idea on release date?