This commit is a refactoring of the 's_parallax' snippet. Note that it
is compatible with previous parallax snippet (old snippets are just
transformed into the brand new one on page load). Note that scroll
speed are changed by this implementation though.

This solves several issues:

- Bg image went easily off of the frame if scroll speed was too fast

- The 'scroll speed' effect was visually inconsistent across different
    devices.

- If the Bg image was smaller than the frame (condition which occurs
    often in a responsive environment), then the image was totally
    offset.

- Since the previous implementation use background-position property
    to perform the effect, It was not possible to define an image
    focus point.

This implementation solves the previous issues introducing a safe-area
that limit the effect range. It's calculated dynamically, according to
the current screen size and the 'speed' option.

The effect if now achieved thanks to the translation of a DOM element
instead of background-position changes. This allows to solve the last
mentionned problem and improve performance.

The implementation rely on the new animation methods of the snippets
Animation class.
As this use the "requestAnimationFrame" function, the snippet knows
the right time to repaint itself, instead of using the "scroll" event
which is triggered too many times and thus occurs between painting
frames. This change greatly improved performances (CPU/painting usage
many times smaller).

This commit extends the behavior of the Animation class of the
"web_editor.snippets.animation" module.

Now, all animations can easily define an animation algo update without
much caring about performances. All that must be done is:

* If the "start"/"stop" method is/are defined, do not forget to call
the _super parent method (which will now initializes the animation
components).

* Define particulary-named method in your Animation class extension.
See in-code comment of the _prepareComponents method.

This extension should be used to define all animations. For example the
use of $(window).scroll(function () { /* do stuff */ }) is now the same
as defining the function with on_scroll: function () { /* do stuff */ }
except that the later one will be more efficient, smoother and allow
you to not care about throttling / event binding/unbinding / ...

Closes #14336

As there is no reason to remove it each 2 saas, there's also no reason to put it back alternatively.

Add 2 fields stored to allow make all in one search and
not postprocess the list of partners.

Allow partners with grades to add their own opportunity in their own pipe.
Until now, it is their saleman which import the opp in csv.

- Remove 'optional' informations in small screen

- Disable ecom popup on xxs device

- Don't disturb customer during checkout, we remove the footer and extra right
  column during the checkout step, address step and payment step.

Confirmation page - remove useless label
Don't center total in xs width
Don't display wizard in xs width
Remove dublicate border in xs width
Show sorted by label

task-28865

Fix commit 537b919e
Don't change the lib file directly.

Partial revert of #2013dc38

Schema is not updated, but it can break if views are not updated.

The translations have been removed but was not fetch due to --minimum-perc argument

Purpose:
In the many2one dropdowns the font is not the same than elsewhere in the webclient

This option is no more implemented since the refactoring of ir.qweb
Gzip (in nginx) do the same and better...

It was already working without it since commit e01837d2

Old code return the user of the partner and not the saleman ! Thanks to the migration :/

Use record / records instead of deprecated locals

It seems Paypal does not always send the same responses on auto-return
even when PDT is off. Although not reproducible on a Paypal sandbox,
sometimes the system auto-return to /payment/paypal/dpn without any
meaningful POST data. This seems to only happen with new accounts
that use the 'Hermes' web application of Paypal.

The correct thing to do would be to add a new field on the paypal
payment provider for PDT token and make the PDT flow available
to users; but this is a stable branch and this fix is already
sufficiently delicate. This shall be done in master though.

From this revision on, users can then activate PDT on their paypal
account, set the PDT token as an ir.config_parameter value (WITH
GROUP RESTRICTION SET TO ADMIN/SETTINGS GROUP!!!) and the system
will process these requests correctly.

test_sale_stock_lead_time.py compares dates and expect them to be the same.
Sometimes, the dates would differ by a second, because they are generated at
different moment during the execution.

This commit adds a tolerance of 1 second when comparing the dates.
(and changed from comparing Datetime strings to comparing timedeltas)

test_sale_stock_lead_time.py compares dates and expect them to be the same.
Sometimes, the dates would differ by a second, because they are generated at
different moment during the execution.

This commit adds a tolerance of 1 second when comparing the dates.
(and changed from comparing Datetime strings to comparing timedeltas)

Automatic tour should not open the kanban record directly in edit mode.
This "edit" link wasn't working and has been fixed by 2e0a3000.

There is a multi-company record rule on `res.partner.bank`,
meaning you cannot see the bank accounts of other companies.

Making a constraint on `sanitized_acc_number` alone prevent
to create a same bank account into different companies,
while you cannot see this bank account from the other
companies.

In this case, the user tries to import its bank statement,
and it contains a bank account which already exists
in the database but for another company than the one
he is currently importing the statement, and,
 - it cannot find it because of the multi-company rule,
 - it cannot create it because of the constraint

The constraint must take into account the company

opw-690969

You are not supposed to write anything in an onchange,
the result of the onchange must be assigned in the given fields
of `self`

This is an oversight during the migration to the new api of the module
in the below revision:
053982f4

opw-694053