[FIX] account_anglo_saxon: correctly set the accounts for returns

The generated moves on a return should be the reverse of the outgoing move.
Fixes #1817, opw 604417
[FIX] mail: chatter read more/less expand first oe_msg_body_long/short in the first oe_msg_body

Otherwise, if the mail itself contains a oe_msg_body_long (because sent in the mail history), it will open that one
[FIX] stock/purchase: dates and currency rates

Use the currency rate of the purchase date instead of the one of at the reception time (opw 610430)
[FIX] hr_timesheet_sheet: avoid error when sort attendances

When an attendance line is edited, the tuple has no key 'name' which lead to a traceback.
Fixes #546
[FIX] Theoretical quantity for created inventory adjustment should take into account location in context of stock
[IMP] Scheduled time, weights, remove routing on lines
[IMP] Purchase order wkf optim
[FIX] Basic patches for product_extended
[IMP] MO should pass warehouse + improvements on pack_operation_ids when someone would make it visible
[IMP] Purchase on incoming shipments with services added
[IMP] Use display_name instead of partner_ref
Merge pull request #2502 from odoo-dev/8.0-wmsstaging9-jco

8.0 wmsstaging9 jco
[FIX] Package: Debian, Windows: more odooification; Debian: correct Packages.gz
[FIX] css: move overflow auto from body to webclient to prevent some element from triggering anoter scrollbar
[FIX] announcement_bar: computed height was wrongly computed
[FIX] website_sale: only display payment method from the same company as the order
[FIX] correctly expand many2ones in autocompletion

The ManyToOneField widget evaluated the domain before doing a name_search,
but the domain should not be evaluated client side, because it can only
be static at that point. It caused crash in autocompletion because
some variables could not be found in the context (see stage_id in
project.task for example)
[FIX] event: subscribe customer error

The onchange methods needs to work with browse records and address_get returns an id. Fixes #2484
[IMP] fields: reset decimal precision on new-style fields

When a decimal_precision record is created/modified, the float fields of the
models in the registry must be reset.  This was done on old-API columns only.
It is now handled by the new-API fields.
[IMP] gamification: usability and shit

Challenge
- 'Reward as soon as every goal is reached' box checked by default (most of the time people want this behaviour, few special cases were do not)
- Click on challenge kanban opens goal list instead of challenge form
- Add button 'Start Challenge' clicking on statusbar is not intuitive

Badge
- When creates a challenge from badge view, set by default badge to 'For Every Succeding User' field
- replace filter 'Current' vs 'Passed' by 'Running' (in progress and done with not reached end date) vs 'Done' (done & failed without end date or end date passed)

Goal
- list of badge on employee form not the first tab