Bug in bean wiring for MongoClient

[shoebjoarder]

When I build using Docker Compose, a bizarre behavior is observed. Sometimes, the openlap database is prefilled with internal data or OpenLAP (analytics techniques, visualization, etc.), and other times, when rebuilding with Docker Compose, the learninglocker_v2 database is created and prefilled with the internal data of OpenLAP.

[shoebjoarder]

The MongoClient configs inherit the same @Bean method names from AbstractMongoClientConfiguration (notably mongoClient and the factory behind mongoDbFactory()). This is causing bean name collisions and/or "last one wins" overrides depending on load order. Sometimes the "secondary" client/factory/template is treated as the default, leading repos to point to the wrong DB.

This bug should be fixed in 17d2291.

[ralf-berger]

Updated Docker Compose and Kubernetes config, please test.