[FIX] sale_stock: product_id_change_with_wh should not call another method (product_id_change) using super, but self. Otherwise some overrides are lost, leading to issues with event-related products.

Some many2one fields happen to have several corresponding one2many fields,
typically with different domains. It is also the case for the field 'res_id' of
mail.message, where each model inheriting from mail.thread defines a one2many
based on that field. The fix ensures that when a relational field is updated,
all its inverse fields are invalidated.

The default values are computed by evaluating fields on a new record. The fix
retrieves values from the cache earlier, because in some cases, the evaluation
of a field invalidates a formerly evaluated field.

[FIX] ir_actions in website: allow to compute website_path even when creating a new server action (avoid crash then)

[FIX] stock_landed_costs: fixed several issues related to the computation and the accounting entries creation. Added a yaml test to cover the different split methods

[FIX] website_quote: Must remove id created by the javascript of scroll spy.

[FIX] website_quote: scroll spy is crazy if the user change quote template. Must remove id created by the javascript of scroll spy.

The extra parsing check is not necessary when we're
not validating inputs, because in that case the
values come from the database and are valid.
The validation is quite expensive due to calls
to strptime() + strftime().

This can give a performance boost on large databases
and should not be a concern in terms of access control
as the inheritance already grants access to the parent
records.

Avoid reading one record at a time, leading to multiple
calls to read() which is special-cased and even slower
than a normal one.

management to access documents in notification emails, as well as for the
'view quotation' link in portal_sale module.

models: added a get_access_action method: basically, returns the action to
access a document. It uses the get_formview_action by default (form view
of the document). However for some documents we want to directly go to the
website, leading to an act_url action for some documents. This method allows
this behavior.

portal_sale: get_signup_url now uses the mail.action_mail_redirect method
instead of directly redirecting towards a portal menu. This allows to fall
back on a standard behavior.

portal_sale: get_formview_action updated, to match actions tailored for
portal users.

website_quote: get_access_action of sale order updated. If the sale order
has a template defined, the returned action is an act_url (website view
of the quotation), not the form action anymore.

mail: fixed signature + company signature in notification emails. Even without
user signature, the company signature + access link should be correct.

portal: signup url in notification emali was not using the mail redirection
as action. It is now the case.

[FIX] email_template: when generating body containing the user's signature, add it as html as it is now pure html, not plaintext anymore.

[FIX] tools: html_sanitize: keep mako tags (<% ... %>), required for example in the portal sale quotation email.

manual fix of fp-style merge

[FIX] mail: compose wizard: fixed default_get overrides not correctly managing the received field_list + improved custom call to default_get to correctly manage its in and out values.

[FIX] crm: fixed day_open and day_close computation (conditional store + be sure that date_open and date_closed fields are set)

[FIX] project_issue, resource: fixed computation of hours / days to open (assign) or close an issue. Those fields now have a conditional store, because they were not recomputed even when changing date_open and date_closed. Changing the stage now correctly changes the date_closed. Also added some fixes in resource module, the date was not correctly taken into account when computing the number of working hours between two dates.

Due to the use of a sudo env, the records
were being added to the sudo cache one by
one instead of all at once. This meant the
prefetching was not able to load all
records at once, leading to prohibitive
times when processing thousands of
records.

+ correct tests