Avoid unnecessary bridge method resolution around getMostSpecificMethod

[jhoeller]

Following up on #21843 in 6.1.3, it turns out that this commonly causes performance regressions, unnecessarily introspecting non-annotated methods in complex class hierarchies on startup. Revisiting the algorithm in BridgeMethodResolver#findBridgedMethod and its use in AutowiredAnnotationBeanPostProcessor and co, these performance regressions should be remedied as of 6.2.13, with introspection performance even having improved over pre-6.1.3 now.

[github-actions]

Fixed via 6f81cb6

[sdeleuze]

With Petclinic, this change allows to go from 435 to 105 invocations of BridgeMethodResolver#searchCandidates during the startup!

As those invocations were also performed with Spring AOT, this will translate in a very significant reduction of the remaining reflection invocations.

It will also improve native image compatibility by avoiding reflection hints on some bean types previously processed.