SpringBoot DependsOnDatabaseInitializationPostProcessor re-declares bean dependencies at native image runtime

This issue is motivated by the following issue in Spring Cloud Task: https://github.com/spring-cloud/spring-cloud-task/issues/880

The DependsOnDatabaseInitializationPostProcessor of DatabaseInitializationDependencyConfigurer declares dependencies between beans and is executed both during AOT processing and during start-up in the native image. On the one hand, this is surprising as analyzing bean dependencies is something the AOT processing should do instead of the native runtime, if I understand correctly. On the other hand, it easily leads to circular dependencies between initializers whose detectors have the same order. If detectors have the same order then the effective order of initializers is ill-defined and can differ between AOT processing and native image runtime.