[IMP] enable loading custom models/fields and views from module data files

Loading views for custom models from module data files was not possible because
custom models and fields were introduced into the registry after all modules
were loaded.  As a consequence, the view architecture did not pass the checks.

This patch takes a different approach: custom models and fields are loaded
early on in the registry, so that views can be validated.  The trick is to take
special care of relational custom fields: we skip them if their comodel does
not appear in the registry.  This allows to install and upgrade modules that
create/modify custom models, fields and views for them.
[IMP] registry loading: setup models only if necessary

When loading the registry without any module installation/upgrade, models are
set up once instead of twice.  In other cases, models are always set up before
installations/upgrades.
[FIX] web: reordering in editable list views

Broaden the set of conditions where reordering is allowed. Lists can be
reordered when they are sorted by sequence (or sequence ASC)

opw-619465
[FIX] hr_holidays: Add missing context check

Fixes #4341
[FIX] odoo.py fix fetching of git remotes

remove the useless heads in local refs so that:

git checkout -b master odoo/master

and

git checkout -b master-name odoo-dev/master-name

works.
[FIX] website_sale perfomance on public categories

Use a domain instead of python filtering when loading root categories.

Closes #4324
[FIX] payment_buckaroo: copy values dict to avoid altering original dict

_buckaroo_generate_digital_sign uses the values dict to generate the shasign
At some point, it alters the dict, it removes BRQ_SIGNATURE, but, as the values dict was not copied, it altered the original dict.
So, the key BRQ_SIGNATURE was not anymore present for methods called after _buckaroo_generate_digital_sign.
For instance, the overriden method form_feedback of website_sale payment
Merge pull request #27 from odoo/8.0

update all commits