[Junie]: feat: implement recipe for constructor injection conversion

[jetbrains-junie]

📌 Hey! This PR was made for you with Junie, the coding agent by JetBrains Early Access Preview

It's still learning, developing, and might make mistakes. Please make sure you review the changes before you accept them.
We’d love your feedback — join our Discord to share bugs, ideas: here.

• 🔗 Issue: Replacing field injection with constructor injection #557
• ⚙️ Trigger: Issue
• 🏷 Title: Replacing field injection with constructor injection

📊 Junie Summary

A new recipe was implemented to convert Spring field injection to constructor injection, handling @Autowired and @Qualifier annotations. The tests initially failed due to formatting issues and handling of existing constructors, but modifications were made to address these problems. The updated recipe is now being tested in hopes of achieving the desired functionality correctly.

[github-actions]

Some suggestions could not be made:

• build.gradle.kts
  • lines 147-146

[knutwannheden]

@jetbrains-junie Note that most of the new tests are failing. For types referenced from Java source files in tests (using Assertions.java()) it is correct to configure the classpath dependencies via JavaParser.Builder. But instead of using the classpath() method the dependencies should be configured using classpathFromResources() which indirectly loads the dependencies from the recioeDependencies configuration in the Gradle build script. Please see other tests for how that is done and note that the configuration often includes multiple versions of a given Maven artifact and thus often needs the dependency to be specified in a way that uniquely prefix-matches the artifact file name as in "spring-beans-5" for example.

[jetbrains-junie]

Hey, it’s Junie by JetBrains! I started processing your request 🚀

[jetbrains-junie]

A pull request updated classpath dependencies to classpathFromResources() for tests converting Spring field injection to constructor injection. Despite these changes, seven tests failed due to formatting discrepancies and issues with annotation recognition. Further adjustments are needed to resolve these failures.

[github-actions]

Some suggestions could not be made:

• build.gradle.kts
  • lines 147-146

[timtebeek]

@knutwannheden What would we want to do with this PR? There's parallel classes doing the same thing. Should we consolidate and attempt to get this merged? Or just abandon and try again with Claude?