Fix build against Spring Boot 3.5.5

[kagkarlsson]

Getting a test-failure for spring boot 3.5.5. Need to investigate and fix:

...
 Caused by: java.lang.IllegalStateException: @ConditionalOnMissingBean did not specify a bean using type, name or annotation and the attempt to deduce the bean's type failed
 	at org.springframework.boot.autoconfigure.condition.OnBeanCondition$Spec.validate(OnBeanCondition.java:630)
 	at org.springframework.boot.autoconfigure.condition.OnBeanCondition$Spec.<init>(OnBeanCondition.java:577)
 	at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchOutcome(OnBeanCondition.java:142)
 	at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:47)
 	... 102 more
 Caused by: org.springframework.boot.autoconfigure.condition.OnBeanCondition$BeanTypeDeductionException: Failed to deduce bean type for org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration.micrometerClock
 	at org.springframework.boot.autoconfigure.condition.OnBeanCondition$Spec.deducedBeanTypeForBeanMethod(OnBeanCondition.java:659)
 	at org.springframework.boot.autoconfigure.condition.OnBeanCondition$Spec.deducedBeanType(OnBeanCondition.java:649)
 	at org.springframework.boot.autoconfigure.condition.OnBeanCondition$Spec.<init>(OnBeanCondition.java:570)
 	... 104 more
 Caused by: java.lang.ClassNotFoundException
 	at org.springframework.boot.test.context.FilteredClassLoader.loadClass(FilteredClassLoader.java:113)
 	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
 	at java.base/java.lang.Class.forName0(Native Method)
 	at java.base/java.lang.Class.forName(Class.java:467)
...

[maxhov]

I looked into it and I was able to fix it by removing MetricsAutoconfiguration.class from the ApplicationContextRunner configuration. I think the failing test it_should_provide_noop_registry_if_actuator_not_present needs to be run with a dedicated configured context runner.

RCA -> In 3.5.0, they merged this change: spring-projects/spring-boot@b722430#diff-29fff29401705fb6efc7af396896a503a3112cfcb288d1ae0a574d1ad922547fR667 how the return type of the bean method is resolved. Instead of directly using the return type name from the method, they first resolve the declaring class, which in the case of this test is MetricsAutoconfiguration.class which is ignored in the FilteredClassLoader and that causes the ClassNotFoundException to be thrown.

[maxhov]

I've created #739 for it.