[FIX] l10n_multilang: remove force_write attribute in process_translations


When processing a translation, the module used to replace the original term by the translated value for accounts (only object with force_write=True).
This lead to only having the translated version for every user, independent of user's language.
On new chart of accounts, will have different account names according to the user preference.
Keep argument force_write in API for stability reason (will be removed in trunk)
[FIX] account: generate the accounts based on templates with untranslated terms (so benefit from translation)
[IMP] l10n_multilang: revert previous change and move it to l10n_multilang, the accounts are now translatable and with the correct source value
[IMP] l10n_multilang: remove force_write from function call, mark parameter as deprecated
[FIX] hr_recruitment: avoid overriding email_from and email_cc in
message_update. This behavior makes sens only in message_new when
setting initial parameter of the applicant, not when somebody sends
an email on the record.
Removed priority change when there is  a 'priority' key in msg; but
this key is not likely to be present in a parsed email.
Removed updated values change due to a mapping of values present in
the email. This code was a copy-and-paste from crm and did not have
any meaning in hr_recruitment.

Also removed unnecessary code in project, project_issue, crm_helpdesk
and crm_claim for the same reasons as for hr_recruitment.
[FIX] l10n_multilang: remove force_write attribute in process_translations
When processing a translation, the module used to replace the original term by the translated value for accounts (only object with force_write=True). Now getting real multilang feature.
Generates the accounts with no language to get the untranslated value
[FIX] document: correct numbering of attachments with the same name