When comparing OS to see if they match for binary cache, we only compare
the lower case distribution name because sometimes "Debian' is
capitalized and sometimes not.

   It helps multi-account users to identify better where the notifications are coming from.

    On  Regularisation Requests context.

     We don't want extra movements been created, so this changes overwrites this behaviour of erp5.

   Invoice display's if user's organisation name (if set, in addition to his) and organisation address (if set replaces his), so his company can be invoiced rather them user.

I had a Theia instance where I installed buildout with `pip install -e --user /path/to/checkout` and later deleted that `/path/to/checkout` and this made it impossible to run instance buildout, failing with import error when importing zc.buildout  in buildout script.

This is because python load user site packages by default. I believe we don't want this, a broken user site package should not prevent slapos from running buildout.

These changes are about running buildout with `PYTHONNOUSERSITE` set, so that python ignores user site packages when running buildout.

references: 

 * https://docs.python.org/3/using/cmdline.html#envvar-PYTHONNOUSERSITE
 * https://docs.python.org/3/library/site.html#site.ENABLE_USER_SITE

See merge request !266

When PYTHONNOUSERSITE environemnt variable is set, python does not load user
site.
User site packages may contain a different version of buildout, which would
be selected when slapos runs buildout, causing unexpected behaviours.

Some buildout profiles are expecting this.

 - Use dict.items() to iterate on dict, instead of dict.keys() then dict[key]
 - don't use six.iterkeys(), this dict is small, so we don't need iterkeys()
   on python2 and can already write python3 version
 - don't % string when invoking logger, logging framework do it for us and do
   it only if message will be logged.

    For historical reason some aggregated packing lists could be merged (due a bug). This changes introduced backward compatibiltiy with those cases, rather them require a data migration.

    This is frequently updated on production and development instances.

Show exactly what type is used for a request, it makes debugging easier.

By default proxy checks if software type is None, then it's setting it to
RootSoftwareInstance, but if it comes as "" (empty string) it's kept as is.

So for consistency with proxy set default software type, so that proxy can
manage it correctly.

    This helps sync ZODB and mariadb (considering mariadb is newer). This is useful when restore a clone or synchronize after restore the mariadb catalog.

   The most appropriated way is reindex the site, however in case of slapos master (with large amount of data) it is too long (make this solution more appealing.

   If the Destroyed Hosting subscription is only present on Invalidated Open Orders, we just skip and converge the Hosting Subscription.

  This means the user deleted everything he had at once, too fast, before everything get processed.

See merge request nexedi/slapos.core!263

See merge request nexedi/slapos.core!262

See merge request nexedi/slapos.core!261

    ... else it leads to nowhere.

      He can access it or open a ticket.

Introduce new "Managed Resources" and assorted fixes accompanying nexedi/slapos!840 

Also respect meaning of verbose (more output in the console) and debug (drop in debugger on errors and keep things around for inspection)

See merge request nexedi/slapos.core!259

Really remove security_uid from roles_and_users table

Don't pollute console output, store this in log file

When we execute crontab commands, these commands might be python scripts, so
we don't want the PYTHONPATH set by `python setup.py test` to apply to these
scripts.

Respect semantics of "verbose" vs "debug", to make it possible to run tests in
debug mode but without verbose messages.

Also adjust "Starting", this message was not clear

No need to query the catalog multiple times for every partitions

In SlapOS software release tests we often have to start a process or store
temporary files in a directory for the lifetime of the test. Cleaning up the
resources is a bit error prone and source of code duplication.

This introduce a registry of resources that are automatically created and freed
by the test framework, to simplify tests.