ref: Remove v5 prefix from react navigation instrumentation to support v6

[jennmueng]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

Rename the React Navigation V5 instrumentation by removing the V5 prefix as the same instrumentation supports both V5 and V6. We still export the reactNavigationV5Instrumentation for backwards compatibility purposes with a @deprecated tag.

💡 Motivation and Context

Resolves #1756

💚 How did you test it?

Tested on an example app with React Navigation 6.

📝 Checklist

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

🔮 Next steps

• Update docs: ref: React Native support for React Navigation V6 sentry-docs#4134

• Add the React Navigation V6 example to the examples repo. Waiting for a release to be made with this PR so the example can have the correct imports.

[bruno-garcia]

Excellent! We just need a migration guide and equivalent patching on the docs 🙏

thanks!

[shamilovtim]

Docs still call out v5 a ton. Might want to change that

[marandaneto]

Docs still call out v5 a ton. Might want to change that

mind sharing the links? I've found only one mention of the v5 name, getsentry/sentry-docs#4255

[shamilovtim]

https://docs.sentry.io/platforms/react-native/performance/instrumentation/automatic-instrumentation/#react-navigation
Version 5 and above

https://docs.sentry.io/platforms/react-native/performance/instrumentation/automatic-instrumentation/#configuration
ReactNavigationV5Instrumentation

https://docs.sentry.io/platforms/react-native/
Performance Monitoring creates transactions automatically for React Navigation v4 and v5; creates spans automatically for XHR and Fetch

There could be more but those are just the obvious ones I saw that confused me