Regression of actuator endpoint error if specified routingKeyExpression or delayExpression

[davidmestr]

Describe the issue
The same problem described in #1614.

When I try to GET the localhost:8080/actuator/bindings, I got a error:

    Could not write JSON: Direct self-reference leading to cycle (through reference chain: org.springframework.cloud.stream.binder.ExtendedProducerProperties[\"extension\"]->org.springframework.cloud.stream.binder.rabbit.properties.RabbitProducerProperties[\"routingKeyExpression\"]->org.springframework.expression.spel.standard.SpelExpression[\"ast\"]->org.springframework.expression.spel.ast.StringLiteral[\"literalValue\"]->org.springframework.expression.TypedValue[\"typeDescriptor\"]->org.springframework.core.convert.TypeDescriptor[\"resolvableType\"]->org.springframework.core.ResolvableType[\"componentType\"]->org.springframework.core.ResolvableType[\"componentType\"]); nested exception is com.fasterxml.jackson.databind.JsonMappingException: Direct self-reference leading to cycle (through reference chain: org.springframework.cloud.stream.binder.ExtendedProducerProperties[\"extension\"]->org.springframework.cloud.stream.binder.rabbit.properties.RabbitProducerProperties[\"routingKeyExpression\"]->org.springframework.expression.spel.standard.SpelExpression[\"ast\"]->org.springframework.expression.spel.ast.StringLiteral[\"literalValue\"]->org.springframework.expression.TypedValue[\"typeDescriptor\"]->org.springframework.core.convert.TypeDescriptor[\"resolvableType\"]->org.springframework.core.ResolvableType[\"componentType\"]->org.springframework.core.ResolvableType[\"componentType\"]) (through reference chain: java.util.ArrayList[1]->org.springframework.cloud.stream.binder.AbstractMessageChannelBinder$1[\"extendedInfo\"])",

With:
spring boot: 3.5.10
spring cloud stream: 4.3.0
spring cloud starter stream rabbit: 4.3.0

The problem is related to ObjectMapper configuration and configurable items of Java type: org.springframework.expression.Expression

[davidmestr]

It’s important to keep this issue in mind because, at the moment (Spring Boot 3.5.x), it can be mitigated with a workaround; however, with Spring Boot 4.x that will no longer be possible.