Single `MongoClientDefinition` handled

Today a single `MongoClientDefinition` is used even if several are provided by the application.

Is that an inherent limitation or a work in progress? I think we should be able to define several definitions.

That might mean that `@Mongo` needs to accept a definition name?
