Consistently use type variant of AbstractDependsOnBeanFactoryPostProcessor dependsOn

[mbhave]

#17805 and #16627 switched to using the type variant for mongo and liquibase.

Potential usages which could be switched are

flyway
cacheManager
quartzDataSourceInitializer

[snicoll]

@mbhave is there a reason this is backported to 2.1.x? I can't help to feel a bit nervous to replace dependency by name to dependency by type in a maintenance release.

[wilkinsona]

FWIW, I think the fix should be made in 2.1.x as it's addressing the same sort of problems as were reported in #17805 and #16627. We categorised both of those as bugs and fixed both of them in 2.1.x.

[mbhave]

Yeah what @wilkinsona said was my reasoning for putting it in 2.1.x

[wilkinsona]

cacheManager does not appear to be affected as CacheAutoConfiguration will back off if a custom CacheManager bean is defined. When it backs off it will take CacheManagerJpaDependencyConfiguration with it. While this avoids the named-based dependency problem, it creates a different problem as defining a custom CacheManager stops the entity manager factory bean from being configured to depend upon it. I've opened #18107.

[wilkinsona]

quartzDataSourceInitializer has been addressed in #17539.