Replaced imports by LodelContext.expose_modules() calls
Theorically all of those imports were tested by unit testing, but we've got no inssurance about that.
And even if unit tests had check for syntax errors, all pieces of code were not tested. We cannot
be sure that an import was missed or forgotten...
Datasources plugins enhancement and loading bugfixes
- now we have a LodelHook to trigger migration handlers loading
- datasources initialization in dyncode is now trigger by a hook (lodel2_plugin_loaded)
- datasources loading by dyncode is better
Deleted datasources plugins and add a settings for datasources declaration
- now datasources are declared with two conf keys : read_only and identifier
- the old datasources plugin hook is now declared in lodel/plugin/core_hooks.py. This file is imported after lodel/plugin/hooks.py in the loader.py
- Implementation of the delete, insert and insert_multi methods + first implementation of the select method in the MongoDB datasource
- Added parsing methods in the mongodb/utils module
[DataSource] added the utils.object_collection_name method to utils module. Added also the insert and insert_multi methods to the MongoDb datasource class
[MongoDbDataSource] Implementation of the connection creation and a first check on the given parameters
- The check method checks, for now, if all the needed parameters are passed to the connection string
- A test class has been written with some bad connection args examples