Spring DI - Fix behavior with named beans

[mcruzdev]

Fixes #45961

This pull request aims to solve an issue when using @Named annotation.

Having the following code below:

@Configuration
public class MyConfiguration {
    @Bean("mySpecialName")
    public String foo() {
        return "foo";
    }
}

The Quarkus SpringDIProcessor will add @Named("foo") (the method name) instead of @Named("mySpecialName") (the bean name), and we will get an UnsatisfiedResolutionException.

This should work properly, getBeanNameFromBeanInstance in SpringDIProcessor does check the value of the @bean annotation to place the correct @Named annotation on the method, but it has a small error: this if statement checks if beanNameAnnotationValue != null instead of if beanValueAnnotationValue != null (beanName vs beanValue).

This change uses the value instead the name, removing the UnsatisfiedResolutionException.

[mkouba]

The fix looks reasonable but I did not check the other parts of the SpringDIProcessor and how exactly we map spring annotations to @Named...

Also pls squash the commits and maybe add a more "informative" commit description.

[mcruzdev]

Yes @mkouba I will do it. It had to be a draft

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 37dc798.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[gsmet]

Looks good, thanks for the fix!