[IMP] account: bank statement reconciliation: correctly find reconciliation proposition based on amount match

[IMP] account: bank statement reconciliation: for a partially reconciled move line, display total and residual amount

[IMP] account: bank statement reconciliation widget: display partner name found in statement import in change partner field ; do not set the partner to false before changing the partner

[FIX] account: bank statement reconciliation widget: display only one line for a partial reconciliation

[FIX] account: bank statement reconciliation widget: refactor fix : is_single_statement -> single_statement

[IMP] account: bank statement reconciliation widget: it is now possible, when reconciliation is done, to close all the statements reconciled and to go back to statements list view

[FIX] account: bank statement reconciliation widget: cleaning (ID has nothing to do in the tooltip showing more infos about a move line)

[FIX] account: reconciliation: taking into account that amount_residual can (very infrequently) be < 0

[FIX] account: reconciliation widget: when updating matches (move lines), exclude those which are reconciled with a selected move line as well

[FIX] account: reconciliation: using move_line.name instead of move_line.move_id.name when is defined

[IMP] account: bank reconciliation widget: making it harder to remove a statement line's partner ; improved change statement name usability

[FIX] account: bank statement reconciliation widget: create move line + partial reconcile now possible

There was a domain in 7.0 but it must be forced
to empty during upgrade, as the MRP BoM model
has changed.

The mapping old api → new api mistakenly takes the last positional argument as
the context (fields_view_get() has an extra parameter after context.)

Fixes issue #2063

When no order is forced, it's more user-friendly if the products are ordered by alphabetical order.
This will mainly be applied:
* In the list view in the back-end
* In the eCommerce, for products with equal website_sequence

The context may be inconsistent (for instance, containing a group_by associated to another
model). The client will take care of keeping it consistent. Fixes issue #1768

name_get() must return a value for each ids and keep order of ids.

The methods product_id_change() and uos_id_change() have been converted to the
new api, and now use the decorator @multi.  When invoked with the old api, by
convention the methods will take the last argument as the context.  But this
will not work properly for those methods, as the context is passed in another
position.  In order to avoid an argument swap in the api wrapper, we moved the
context to its expected position.

Fixes #1943

The compatibility issue with auth_ldap has been
fixed and the default key derivation function
switched to PKDF2+SHA512. `auth_signup` provides
a password reset mechanism that can be used in
combination with `auth_crypt`.

Fixes #1272