The current programmatic configuration makes use of the old 5.0.x config beans internally (injection) as well as unit tests and in SPIs.

We need to refactor this internal code to use the new post-5.1 config beans.

However, the public API (DefaultCacheManager) should still support the old Configuration beans. To do this we'd need to write something like the reverse of the LegacyConfigurationAdapter. The LegacyConfigurationAdapter takes a 5.1 Configuration and creates a 5.0 Configuration. We need to do this in reverse once the internals start using the new 5.1 Configuration.

Note that public API and SPI should still support the old Configuration to allow drop-in upgrades. This includes CommandInterceptor and CacheStores.