More version catalog adoption

[runningcode]

📜 Description

Version catalog adoption

#skip-changelog

💡 Motivation and Context

💚 How did you test it?

📝 Checklist

• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

[runningcode]

There’s no way to have aliases or have targetSdk and compileSdk values reference each other.

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	450.92 ms	454.88 ms	3.96 ms
Size	1.58 MiB	2.08 MiB	510.82 KiB

Previous results on branch: no/version-catalog-6

Startup times

Revision	Plain	With Sentry	Diff
54f9bc2	389.91 ms	401.67 ms	11.76 ms

App size

Revision	Plain	With Sentry	Diff
54f9bc2	1.58 MiB	2.08 MiB	510.82 KiB

[romtsn]

do we need to specify it in the root project with the version then?

[runningcode]

That’s a good point, i’ll do this.

It isn’t required but it helps maintain a single classpath for all projects. that should improve buildspeed if we have a single classpath. Our build, however, is a bit tricky since different subprojects use different versions of the same plugin (like spring) so the buildscript classpath cannot by synchronized 100% for now.

[runningcode]

Actually it looks like gretty depends on spring boot and since we don’t have spring boot in the root buildscript classpath, this causes conflicts.