Detect SDK dependency version mismatches

[lcian]

📜 Description

Adds a new task validateSdkDependencyVersions that checks for dependencies in the io.sentry group (except for the plugin itself and the core SDK io.sentry:sentry, as an explicit dependency on the core SDK module could be valid if the intention is to override the default version used by the plugin) and validates if they have consistent versions.

Currently, customers would need to add

<goal>validateSdkDependencyVersions</goal>

to their pom.xml to enable running this new task.
I need to investigate on how to make it run automatically by default.

💡 Motivation and Context

Closes #123

💚 How did you test it?

I have tested different scenarios manually with the example project included in this repo.
I have also added integration tests, but it seems that they are not running this new task, even when explicitly specifying it as an execution goal.

📝 Checklist

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

🔮 Next steps

• Fix integration tests
• Have the task run automatically in the validate phase (not possible)
• update changelog
• update docs if needed

[lcian]

Need to check what happens with the BOM as well

[lcian]

Added some tests scenarios where the BOM is used as well.
The tests are still not effective as described above.

[lbloder]

@lcian afaik there is no simple way around setting <goal>validateSdkDependencyVersions</goal> in the execution tag of the plugin. So this is fine with me.

[lcian]

@lcian afaik there is no simple way around setting <goal>validateSdkDependencyVersions</goal> in the execution tag of the plugin. So this is fine with me.

That's a shame, would've been great to have this run automatically without customers needing to enable it.