[FIX] account_analytic_plan: correctly check context

The id of the journal is passed in the context. Avoid trying to browse on jounral_id=False
Fixes #821
[FIX] yaml tests: extra key in on_change result isn't that bad.

In the return result of an on_change, having keys which are not ine the view is not that bad, it is not an actual problem.

Display warning instead of asserting all the keys are in the views.
[FIX] account_anglo_savon: round prices according to account precision to avoid getting unbalanced move

The standard move_line_get from account.invoice returns prices rounded (price_subtotal field as account precision) while the anglo-saxon module could return dict with non-rounded prices.
With amounts with bigger precision, we could get a difference of a few cents when comparing the debit/credits and then not be able to balance the invoice (opw 597208).
[FIX] pos: display cashier name on receipt, not the user
[FIX] Calculate date interval using super user time zone

When you set the date of a cron the July 1st at midnight, if the user
time zone has a positive offset, then the converted UTC date is the
June 30th and adding 1 month will end up on July 30th translating to
July 31th instead of September 1st.

To solve this issue we use the super user time zone for the date
calculation.
[FIX] web_kanban : resequence column and content by drag and dropping
[FIX] yaml tests: Set on_change keys not in view logger as debug instead of warning

This is related to commit d31faceb67fd87acaca00365dcfc28925b08a37f
(This is to avoid the runbot being yellow if on_change methods have extra keys in the returned value, this is not wrong, the web client will simply ignore them).
[FIX] web: image fields re-render on next/previous

By default, on binary images read, the server returns the binary size
This is possible that two images have the exact same size
Therefore we trigger the change in case the image value hasn't changed
So the image is re-rendered correctly
[FIX] procurement: refactor scheduler so it continues even if a procurement failed

If the mrp scheduler fails during the treatment of a procurement (due to a postgresql error, like an update lock), we let it try the other procurements, instead of stopping at the first procurement which fails.
Besides, we retry to treat the procurements which failed, until the list of the remaining procurements is always the same (meaning something is wrong and block the procurements treatment).
[FIX] l10n_be_coda: set a meaningful filename default value
[FIX] mail: to/from/reply-to addresses formated according to RFC2822

Use formataddr method from email.utils lib, which do the job correctly
[FIX] portal_claim: create claim with no partner_id

If partner_id is False, do not try to name_get

This fix is related to the rev 095be21ab17f7f731877d61c99b48b51119ff39a
[FIX] web: missing self initialisation

The self is needed in the _value() method below, opw 608878
[FIX] account_anglo_saxon: avoid duplication of price difference lines

When computing the price difference lines, in move_line_get of account_anglo_saxon, we loop on the result of super call for each lines (n * n times) to compute the price difference.
The product_id was used to match the returned line and the original invoice line. This was wrong as we could get several lines with the same product_id (and then get n * n price difference lines).
This patch adds the line id to the result of move_line_get (from account) so that account_anglo_saxon can filter more efficiently and only get one price difference per invoice line.
Fixes #704
[FIX] web: on switch form (from list & kanban) do not load record if empty dataset
[FIX] account_followup: avoid crashing when a move line has no ref
[FIX] portal_sale: browse data for payment acquirer form with superuser ID

The payment form needs to be rendered for non-employee
users, and may require accessing extra financial data
not available for those users.
[FIX] account.invoice: payments can never be shown to portal users, but residual might be needed

The residual amount is typically needed to render the
online payment forms (payment acquirers).

Payments on the other hand rely on account.move.line,
something that portal users should never be allowed to read.
Removing the field from the view by setting a model-level
group permission ensures they will not see an error.
[FIX] export: add the context in the export

In some cases, the data dispalyed in a list depends on the context
This context needs to be passed to the export method, so the exported data reflects correctly the data from the list view
[FIX] context_timestamp MUST return a "timezone aware" timestamp