The options table displays the following columns:
Product name | Description | Price
while the pricing table ommits this first column. This is quite a
good idea as products are not always accessible to portal/public
users depending on what modules are installed (notably website_sale
which introduce the published/unpublished record rule on products).

To avoid introducing an extra-sudo simply for display reasons,
this commit simply remove the product name column and harmonizes
the options display with the main pricing display.

Somehow in the migration to the new api, it was decided that the
acquirers would be browser as sudo only for token access. This caused
portal users to have a crash when trying to view their quotation since
some fields from acquirers are set the specific groups for security.

This commit reintroduces the old behaviour, which was to browse as
SUPERUSER in all cases for the rendering of the buttons.

`customer_email_data` can be undefined.
It must therefore be checked before testing
its length

e.g. use the /helpdesk command with an anonymous visitor
of the livechat

opw-690301

Change color #a24689 to #875A7B

Commit https://github.com/odoo/enterprise/commit/8ac1c19fac7615fecd51e670f798d13158a4e53c
changed the odoo interface violet by changing the main LESS variable
but forgot there was many direct occurences in XML/HTML/... (for
example for the mobile browser color).

Even if it's community the odoo interface violet is used at many places
(module description, XML demo data, ...).

A customer can confirm a quotation only once `website_quote` is
installed. Without it, this isn't possible, and by default
this is not installed with the installation of the `sale` module.

Courtesy of fgi@odoo.com.

Commit 48a1eaf7 adapt the welcome
message on website so that it fits the page height. But this does
only worked for large screens as the height was forced to main
height... which is smaller than the default welcome message height
on small screen. The fix only had to use min-height instead of height.

Commit 5f980404 in saas-12 changed
some "saved" event to "save" event but forgot to adapt new features
which depend on this in 10.0 after forward port.

The blog_cover JS code is only available on blog pages. So the option
can only be activated on blog pages (which was not the case if the
snippet latest post was used on a random page).

Animation preview on images did not work as the web_editor stopped
every potential animation when an image entered edition. As the
behavior does not seem useful as there is no infinite animation which
is possible with standard odoo (and even if it was the case, it would
not be too strange that the animation continues), the feature is
removed with this commit.

Since commit 8ac1c19fac7615fecd51e670f798d13158a4e53c the odoo brand primary color
changed, which also changed the color of tips. The problem
was that they lose a lot of contrast in the appswitcher.

  - Before it need a tap to show options
  - And Tap area was not enough for mobile

Since the library nestedSortable was updated to the release 2.1a,
at the below revision:
https://github.com/odoo/odoo/commit/aa19d9edd02756d87056a44340e36568b3183e21
It was no longer possible, in the front-end, to move the menus:
Re-sequence them, put one below another, ...

Indeed, in that piece of code, `.item_id` was never
set with the new release, while it was the case with the former one.
We replace with `.id`, which looks like to have the same behavior.

[FIX] hr_attendance: get group via xmlid instead of searching via name match (which will not works in other languages)

couldn't find a group after rename. -> renamed

- improve some help messages
- improve comments
- small refactoring
- add category to group "Manual Attendance"

for coherence with menus (that got renamed after code was written) to improve
code comprehension.

Also, attendance is an application.

As the field is not shown in the view, it is just done
because the field is still there and easy to do.

As the finished move or the one after might automatically split into its components,
it is not a good idea to select a Phantom BoM for a production order, so
this is for the moment, the best way to avoid it.

[FIX] mrp: when posting inventory in mo, don't allow to pass stock.move.lots with quantity done > 0, but without lot

It is good to have this check, otherwise
it risks taking whatever lot or creating
a piece without lot if you would by accident
say you did so many quantities but no lot was given.

Before this fix, the link was always present, even if no acquirer payment was configurated to allow tokenization.

Stay coherent with others buttons from eCommerce.

Old terms feature display the default terms from company.
But if you have more than that 10 words, it was just unusable.
Now, we just add a link to a page.

The payment method and pay now button was not in the left part.
So if we only have one line in cart, a big margin top was visible.