The one2many field 'user_ids' was initialized with an incorrect value for the
inverse field 'wizard_id', using a res.users id. The latter was causing a
MissingError exception. The fix is simply to not define explicitly the inverse
field in the one2many.

Also did a small cleanup of the code of the wizard.

(partial revert of 44a5268c)

The existing code was buggy when writing on *2many fields with a list of
commands: the value was converted for the cache, but taking an empty recordset
as the current value of the field.

[FIX] hr_contract: count the number of contracts of an employee as superuser_id as this field is required in the form view. However no data is displayed, and no data about the contracts are leaked, so no security holes.

Before, the field purchase_ok was set as readonly on the product form if the product wasn't a variant, to avoid users to set all the products variants associated to the product template to be set as purchase able in one action.

We now consider that this can be done by the end user

opw-611106, when clicking quickly Sales > Opportunities than Sales > Leads.

This makes the patching mechanism more flexible, and enables patching BaseModel,
for instance. This should fix #1501.

(rebase of #1534)

It is not useful to try to create foreign keys when the destination model is
a PostgreSQL view for example.
We already do this kind of verifications but ir.actions and transient models
but did not for _auto.

- simplify the code by removing unused cases
- do not modify input argument 'value' of create/write
- do not call BaseModel.read() with reified group fields (this causes warnings)

Mandatory since we changed the structure of the dom since 8.0.

Makes ordering transitions easier and more deterministic.

(Rebase of #1564)

[FIX] account: fix unexpected invalidation of field account_invoice.reconciled

Changing .po files to avoid to retranslate existing terms.
Fixes #1328

[FIX] website_forum: when a user posting a new answer or question does not have a valid email address, redirect to the user's profile instead of crashing when trying to send notifications.

Problem: the field account_invoice.reconciled was invalidated by a workflow
signal sent from the compute method of the field. The purpose of the signal was
to re-open the invoice when the account move lines were no longer reconciled,
for instance after cancelling a reconciliation.

Solution: modify the workflow such that it makes an automatic transition from
'paid' to 're-open' when the condition 'not reconciled' is met. This works
because the field 'reconciled' is stored, and each recomputation forces a
reevaluation the workflow. The signal to re-open the invoice is thus no longer
necessary.

[FIX] sale_stock: invoice createde from picking was not using the prive list from the bom components

In a multi-company environment,
if the user signed in was not working in the company displayed by the website,
he couldn't browse the website

See #1527

Some domains have not been altered according to this rename

When searching for a bom based on a product.product, the method used to return any bom linked to the template (so searching for bom for variant A could return bom for variant B if both share the same product.template).
This will allow to return bom not linked to a variant without returning the one of another variant (opw 609358)

website_quote: renamed validity date to expiry date & adapted the sale order report to display the expiry date in website_quote module instead of sale module

When a new record is returned as the value for a many2one on a new record, the
method Many2one.convert_to_write() now returns a NewID, and default_get() then
discards that value from its result. This makes it consistent with its former
behavior.

Manual rebase of #1547

[REF] website_quote: displayed string of validity_date field changed from 'Validity Date' to 'Expiry Date'

As the survey hardcode lot's of views and reports in python, we do not beneficiate from automatic timezone conversions in the webclient.
Hopefully this is fixed in v8 after refactoring of the survey module. opw 608786

The fix consists in this: when setting up models, ignore manual fields that
refer to unknown models if all models have not been loaded yet.

[REF] mail: same_thread field changed into no_auto_thread, its contrary, to avoid migration issues (adding a 'always False' column is easier than an 'always True').