feat: Add auto-installation for sentry-android SDK and integrations

[romtsn]

#skip-changelog

📜 Description

• Adds auto-installation for sentry-android and timber, okhttp and fragment integrations
• We perform existing dependencies/version checks only for the direct (first-level) dependencies, because the mechanisms Gradle provides do not allow calculating the entire dependency graph at this stage. There's a way to resolve the entire graph (copying a configuration and resolving it), but this is very costly to do at configuration phase, so I'd really not wanna do that. I think this is best effort we do now, and it will cover most of the cases.
• Because of the above I've added an explicit sentryVersion configuration setting, so the users can specify the version, for instance, if they use an older sentry-android version that is coming as a transitive dependency from one of their submodules/libs.

This is what it looks like in practice:

Notice how there are no sentry dependencies in the SS above.
When we build the app, the final apk looks like this (with all integrations and the SDK included):

💡 Motivation and Context

Q1 goal

💚 How did you test it?

📝 Checklist

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

🔮 Next steps

[github-actions]

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

Generated by 🚫 dangerJS against a44bf09

[bruno-garcia]

Maybe I'm wrong to suggest was there instead of is. Or perhaps we should log: installing ayz package since I believe at that point we're just adding it to the list of dependencies.

Perhaps even: Adding package xyz to the dependencies list

[romtsn]

Had to revert back to using singleton to share AutoInstallState, cus build services cannot be serialized (and the ComponentMetadataRules are serialized). Did thorough testing - no problems occurred.

[romtsn]

@marandaneto addressed the comments, you could take another look if you will.