[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