[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
[IMP] calculating nextcall datetime of a cron SHOULD use the cron's user
[FIX] base: revert 19e401a for title on res.partner form

The title of the partner is restricted with a context that will change in the onchange_type. Having twice the same field will not work well.
Remove the invisible attribute as the domain is handled by the domain.
[FIX] portal_sale: remove un-necessary access rights, improve rules

Portal access rights need to be associated with
security rules, or not granted at all, as soon
as they grant access to non-trivial data.
[FIX] portal_sale: remove more access rights, add pricelist access

Pricelist access is necessary for being able to read
the unit price of sale order lines, and does not
pose major security risks, as it does not permit
reading the actual pricelist definition.
[FIX] tools.translate: when loading entries from a PO file, use also the POT.

On Launchpad, as commented on bug 933496, PO entries (and their comments) are
shared between series. This mean that e.g. the 7.0 series can have the wrong
`reference` comments (those beginning with #:) as they would be copied from say
the trunk series. Those `reference` comments are used to import translations
and look them up.

This patch adds a few lines of code to tools.translate so that targets
defined in the POT `reference` comments are used in addition to those from the
PO file.

Also adds a test module to validate the new behavior.

This patch stems from:
 - the 6.1 branch by Vo Minh Thu:
    https://code.launchpad.net/+branch/~openerp-dev/openobject-server/6.1-fix-po-targets-933496-vmt
 - the 7.0 port by Numerigraphe:
    https://code.launchpad.net/~numerigraphe-team/openobject-server/7.0-fix-po-targets-933496-vmt
[FIX] tools.translate: addons path resolution failed with duplicates

When the addons_path config contained the
default path, the system was working with
an empty addons_path in the middle of the
other paths. This empty one matched for all
files, making all files appear to belong to
the root path component, e.g. `home` if the
root path is in /home.
Refactored a bit to avoid duplicates and
redundant path calculations.
[I18N] Update all 7.0 translation templates with latest terms and annotations

Total new terms: 168
Total deleted terms: 95
Total identical terms: 16329
(Some modules skipped, typically all l10n_* modules)
[I18N] Update 7.0 translations with latest changes on Launchpad

See also https://github.com/odoo/odoo/wiki/GitHub-Transition#translations