[FIX] sale_layout: set 0 as default value for categ_sequence

Otherwise, in some cases, the categ_sequence can be set to null, which is not ordered the same way than 0, and you won't be able to sort lines with null and 0 as categ_sequence between each others
[FIX] website_forum: Forum, use old API in v8. forum was not a browse record, so we need to re-browse. Tags: Force to delete tag. Before old tag deleted was not removed from relation, Now we use a 6 to force the update, followed by 0 to create.
[IMP] When no stock moves, change whatever you want, otherwise no change at all for UoM.  #3440 Enhancement request richard-willowit

The default UoM can only be changed when there are no stock moves (or only cancelled ones), but to any category.
The purchase UoM can be changed whenever you want, but has to be in the same category as the default UoM.

Closes #3440

[IMP] When no stock moves, change whatever you want, otherwise no change at all for UoM.  #3440 Enhancement request richard-willowit

[FIX] Remove line

[FIX] Constraint should be applied when UoM or PO UoM is changed
[REV] product: rev. 42f5114 needs further review

Incorrect use of stock.move in product module + needs review.

This reverts commit 42f511405a4efe88e3903a4b4040ec9d83e462e2:
"[IMP] When no stock moves, change whatever you want, otherwise no change at all for UoM.  #3440 Enhancement request richard-willowit"
[FIX] openerp: don't ignore active field on new views when updating a module

Without this fix, if you have a new view in a module with active=False, the active tag will be ignore when upgrading the module because of 'update' mode, and the view will be activated by default !
[FIX] purchase(_requisition): typo negociation -> negotiation
[FIX] web: force company_logo change on company change

In multi company environment, the company logo was not updated on company change in the user preferences
This disrupted the end user, as he might think the company change did not happen.
[FIX] web_graph: pass context to fields_get for translation

In graph views, fields from the pivot table were not translated in the user language
We pass the context, containing the user language, to fields_get in order to get the translation
This is also done by the search view, in search.js line 1978 at this rev.

opw-616713
[CHG] ws doc: set right section against a dark background
[FIX] doc: viewport meta missing
[IMP] ws doc: affix language switcher to page top
[FIX] fields.py: Many2one fields only put valid values in cache
[FIX] web: m2o search facet do no set `default_*` context key for "name_search" values
[FIX] fields.py: in many2one convert_to_cache, value can be int but long as well
[FIX] translate: lang detection fallback actually falls back

For instance, when a context was passed to a method, but no lang was defined in the context, it did not tried to fallback to other places where we could have find the user language.
[FIX] account: floating point comparisons in get_reconciliation_proposition
[FIX] enable --debug for non-xmlrpc contexts

fixes #3102
[IMP] account: account.statement.operation.template model
- better many2one ondelete strategies
- domain set on fields, not views
- added domain on analytic_account_id field
[FIX] Customers remove action domain customer=1 use the context default.

Closes #3902
[IMP] res: partner form replace widget selection by option no_create