Set acceptTransitive to true for JSpecify recipes

[scordio]

What's changed?

Prior to this change, the JSpecify recipes add org.jspecify:jspecify as a dependency, even for cases where the dependency is already available transitively.

Now, acceptTransitive is set to true, so that the dependency isn't added when it's already available transitively.

What's your motivation?

• Fixes Avoid adding org.jspecify:jspecify when running MigrateFromSpringFrameworkAnnotations #757

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[scordio]

• I've added unit tests to cover both positive and negative cases

Is there any test case I could use as an example to verify the behavior with transitive dependencies?

My best guess so far is to duplicate the existing methods in JSpecifyBestPracticesTest and add something to the POM that brings JSpecify transitively. To be precise, spring-core would be what I'd add to the MigrateFromSpringFrameworkAnnotations test case but I'm unsure about the other cases.

[timtebeek]

Only spotted this now! Sorry about that, I don't get notified about drafts. Looks perfect to me as is; no need to add tests beyond what we already have for this one in particular. Thanks a lot!