Decouple `BeanDefinitionRegistryPostProcessor` implementations

[snicoll]

While reviewing an issue in Spring Framework, I've noticed that Spring Integration has BeanDefinitionRegistryPostProcessor implementations that are also doing something else.

We're considering reviewing this contract so that such post-processors are automatically excluded from AOT processing (as they operation on the bean factory that's pre-processed by it). Can you please review DefaultConfiguringBeanFactoryPostProcessor and MessagingAnnotationPostProcessor so that they only perform bean definition registry post-processing and nothing else?

[artembilan]

Sure! What deadline should we aim this for, please?

[snicoll]

If we change something, it will be in Spring Framework 6.1 at the earliest. Thanks!

[artembilan]

Reopen for MessagingAnnotationPostProcessor part.