[FIX] module.loading: ensure installed modules are all loaded before installing new ones
[FIX] module.loading: ensure installed modules are all loaded before installing new ones

After the recent change to make module install
atomically (code *and* data), we ran into issues
when installing a new module indirectly triggers
code of a not-yet-loaded-but-installed module,
via its data that is already in the database
(e.g. worflows or reports modified by this module
within another module, that now refer to its
code).
To avoid this, we now make sure that we only
install new modules on top of a consistent system
(code *and* data), by loading all installed or
'to upgrade' modules *before* starting to install
new ones.
MarkusTeufelberger/openobject-server,vnc-biz/openerp-server,vnc-biz/openerp-server,splbio/openobject-server,gisce/openobject-server,gisce/openobject-server,MarkusTeufelberger/openobject-server,ovnicraft/openerp-server,splbio/openobject-server,gisce/openobject-server,MarkusTeufelberger/openobject-server,ovnicraft/openerp-server,splbio/openobject-server