Invalidate instrumentation cache when changing instrumentation features

[lbloder]

📜 Description

Add features, logcatEnabled and appStartEnabled params to SpanAddingClassVisitorFactory parameters to make sure that if these change, the instrumentation is run again and the cache is invalidated.

💡 Motivation and Context

Currently, when instrumentation parameters features, logcatEnabled or appStartEnabled change, instrumentation is not run again and the cached instrumentation result is used. I.e. it is not possible to change the feature set without deleting the gradle cache in the home directory.

Fixes #3595

💚 How did you test it?

Added automated test

📝 Checklist

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

🔮 Next steps

[adinauer]

@romtsn do you wanna review this one?

[markushi]

LGTM!

[romtsn]

LGTM, nice work!

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Invalidate instrumentation cache when changing instrumentation features ([#753](https://github.com/getsentry/sentry-android-gradle-plugin/pull/753))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against e0a4173