[FIX] web: ensure one2many field destruction on button cancel

The destruction of one2many fields is forced with the event change:effective_readonly
This revision add the forced destruction for cancel(discard) button as well

Otherwise, one2many fields are not properly destroyed when hitting the button "discard" (from save or discard).
This can be problematic for one2many editable list views (such as invoice lines) if you discard while having a mandatory field not filled in the invoice line: You can't recreate an invoice, the one2many editable list is messed up

Use case: Create an invoice, create a line, leave the description, required field, empty. Then, discard. Then, click on create.

opw-616946
[FIX] web: user lang has the priority on partner lang

Potentialy, the timezone too.

On item action click (such as menus in More.. and Print..), the data in form view had the priority on user context (through the sidebar_eval_context)

Therefore, if a field "lang" was present in the form view (like in partner form), the web/action/load xmlrpc call was using the partner language instead of the user language.

Example of wrong use case before the fix:
 - Set the user language in French, then go to a partner form of a partner with English set as language
  - Click on any button of the partner form, such as the "Invoices" button, notice that the last item of the breadcrumb is in English, instead of Frenh (the user language)
  - Click on any menu opening a wizard in the More.. dropdown menu, notice that the wizard title is in English instead of French
  - Print any report from the Print dropdown menu, notice that the report file name is in English. If you print the same report for the same partner but from the list view, the report file name is in French.
[FIX] email_template: default model for save as new template feature

When sending a message with the "Compose new message" button on the right of the user menu, in the top bar, if you tried to save the message as template, you had a traceback because model field of email.template is mandatory, but was set to True because there is no model in such a case.

As there is no any relevant model in such a place, and that the field is mandatory, mail.message is pretty convenient as the default value.
[IMP] account: bank statement reconciliation widget: remove a created line by clicking on it
[FIX] account: bank statement reconciliation widget: do not propose partial reconciliation if there are created lines
[FIX] kanban: respect default_order when a groupby is active

The `default_order` attribute of a <kanban> view was applied
for a non-grouped kanban view, but was simply ignored when
the kanban view was grouped, a common situation.
When a groupby is active, the main order is the column being
grouped, but the `default_order` is still useful as
a secondary sort ordering, within the kanban columns.

This patch complements the original patch of
rev. 5c0804eaef81c237043844382d6456656070fb9f from PR #520.
[FIX] account,sale: show payment term & fiscal position notes in reports

Complete commit 3d88a60
Display payment terms or fiscal position note instead of simple the name.
Fixes #3635
[FIX] purchase: display only one shipping address

The warehouse location is the fallback value
Fixes #4056
[FIX] purchase: access rights when validating a picking

When a warehouse user transfer an incoming shipment, the linked purchase order
is updated as well but the user may not have access to it.
Trigger the workflow as admin instead. opw 619775
[FIX] email_template: missing translations in email template

When composing an email based on an email template, some parts of the template
(the result of name_get on fields) were not translated.
This was due to missing language in context when rendering the template.
Fixes #3708, opw 617309
[FIX] web: retro compatible patch for a8f94a59cde1c4034b1a704014d1572598db833f

Some views are not appended to the element oe_view_manager_body, such as client actions views.
For these cases, we append the element to the view manager element

Besides, we set the appendTo option of jquery ui autocomplete after a first initialization, because of a Jquery ui bug:
http://bugs.jqueryui.com/ticket/8858
[MERGE] l10n_ch: update the Swiss chart of account to the 2015 version

Also adds 2 financial reports: Balance sheet, Profit and Loss
Fixes #3992
[FIX] sale: copy sales team on the invoice from a sale order

Follows 31a01ea, propagation of some fields from sales orders to invoices (when
created on deliveries) have been added but it missed the section_id field (Sales Team).
Fixes #4155
[FIX] base: address layout css

The double % was not understood by some browsers (e.g. Firefox).
No need for escaping in this block.
Fixes #4142
[FIX] google_calendar: All exceptions types do not have read method
[FIX] google_calendar: typo, Google is not plural
[FIX] account_analytic_plans: correct call to account_get

The account_get method has the signature
  def account_get(self,... company_id=None, context=None)

so should use positional argument context=context.
Added missing company_id parameter.

Fixes #4084
[FIX] web: 558efaceadf027a51a049c2df4c570ec590353ac not working for modals.

The above revision, which was already a patch for rev. a8f94a59cde1c4034b1a704014d1572598db833f, did not work properly for modals, like the use template many2one field of the mail.compose.message wizard.

We therefore append the ui-menu selection nearer to the input field.

$el.parent().parent() looks odd, but the goal is to append this selection ui just after the parent of the field, but as jquery ui autocomplete only accepts appendTo (and not after()), we append it to the parent of the field parent.

This fix has been verified for
 * many2one fields in classic form view (with or without sheets)
 * many2one fields in editable list view (embedded in form view or not-
 * many2one fields in wizard modals
 * many2one fields of the bank statement reconciliation widget
[FIX] When all_op_processed False it should still create the links #4149

Fixes #4149
[FIX] models: docstring typo.

closes #4163