feat(multi-module): Introduce SentryRootPlugin with App and Lib subplugins

[romtsn]

#skip-changelog

📜 Description

• Introduce a new io.sentry.gradle plugin that has to be applied on the root project level. The plugin then:
  • Goes over subprojects and applies the respective subplugins depending on what plugins are currently applied to the gradle project
  • AppSubplugin implementation remained untouched and just works, however I will refactor and extract some things later on
  • LibSubplugin implementation to follow
  • Checks if the io.sentry.android.gradle plugin is in place and throws as they are incompatible and can't be used together
• Deprecate io.sentry.android.gradle and print a message to switch over to the new root plugin
  • It also delegates to the same AppSubplugin that is used by the new root plugin
• Factor out common things into a separate file that we share among the plugins

💡 Motivation and Context

Closes #800

💚 How did you test it?

So far just manually, will add/convert existing tests later

📝 Checklist

• I reviewed the submitted code
• [] I added tests to verify the changes
• I updated the docs if needed
• No breaking changes

🔮 Next steps

• Make LibSubplugin do the actual work
  • also investigate if we can reuse the same one for all kinds of libs, not only android
• Make RootPlugin collect sources from all modules into a single bundle and upload it
• Introduce new SentryRootExtension and SentryProjectExtension to allow configuration per-project or globally on a root project level
• Convert tests to use the root plugin and add a single test that tests the deprecated one

[romtsn]

This was a leftover from ktlint -> ktfmt migration

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against b17f9e8

[romtsn]

For some reason this sample doesn't work but I will figure it out later (or maybe drop the sample altogether, as it's problematic to support it given there's no plans to support AGP 8+ from the proguard side)

[runningcode]

I think we should drop this since sample as they don’t support AGP 8+

[runningcode]

do we know if this is isolated projects compatible?
see build logic constraints here: https://docs.gradle.org/current/userguide/isolated_projects.html#build_logic_constraints

[runningcode]

Gradle 8.8+ introduces the isolated project callback where you can call gradle.lifecycle.beforeProject { from settings.gradle to access projects in a limited way.
https://docs.gradle.org/current/userguide/isolated_projects.html#gradle_8_8