When an expense is recorded and linked to an analytic account, the
associated line will appear in the timesheet.

This fix links prevents linking an account analytic line to a timesheet
sheet if the line is not a timesheet.

Somehow related to a4b6e3a8

opw-657917

If the kanban view is loading grouped records, the dataset of the view
itself is the concatenation of the dataset of each groups.

But when using "Load  more..." on a column, these records are not added
in the view dataset which is thus desynchronised. This could lead to an
error down the road.

closes #10156
opw-659016

This revision is related to 7be2403c

The payment acquirers must be fetched if the quote
needs a payment.

Besides, as explained in the above revision, the state
`manual` no longer exists sales orders, and therefore
this must no longer be used to determine if a quote
needs a payment or not.

opw-660575

Cleaning and writing in new API "onchange_employee" and "onchange_contract".

opw:659338

1. To change the page title, you now have to call
`set_title` from `require('web.web_client')`

2. Without the `type="button"`, the `Change Password`
button is regarded as a `type="submit"`, therefore
submitting the form, on `web` on click,
and `web` doesn't expect this POST request.
The POST request must be done on
`/web/session/change_password` only.

opw-660567

When writing an URL in the chatter with a colon inside, the function
"html_keep_url" must detect all the URL.

opw:660116

For performance, we could use iframe with embed document.
But it's more styled to use our own slide design that an iframe
with a long scrollbar.

 - A simple POS user doesn't have the rights to write
   on pos.config, not even to write the `current_session_id`,
   so it must be done as sudo.
 - If no fields is specified to `search_read`, it reads all fields.
   The simple POS User cannot access all fields on `account.journal`,
   (e.g., the computed fields implying `account.payment` records)

opw-659079

This revision is related to 432f199f.

Since the above revision make sure to change the
editable list to `bottom`,
the order of the list should be done on the `date` (asc),
on this view, as this is more likely that, when adding a new line,
that the date set on this new line is
more recent than the dates on the other lines.

The new added line should therefore appear directly at the bottom
of the list, to avoid consufing the user.

Besides, the default order of the model `account.analytic.line`
is set to `date desc, id desc`

opw-659892

After initial implementation CSRF protection had been left poorly
documented tripping up users and developers (#9538, #10139).

Add a warning in the logs for developers, and a more extensive
explanation of the whole thing in the @route docstring (and the official
documentation).

Fixes #10158

rST uses double-backticks for literal text, not single

Allow to arrive on the form with fields prefilled with params in url

Merge branch '9.0-opw-657357-rco' into 9.0

In installation script or documentation

Fixes #10052

task 21446

The default group_by for 'Date Invoice' in 'account.invoice.select'
view must group the 'account.invoice' with the field 'date_invoice'.

opw:660033

Context was a new one instead of updating the existing one. This was
preventing a correct context propagation.

When a product is linked to several "supplier.info" records with
the same name or same product_name, the name or product must only
appear once.

opw:660107

By default, users can only create/edit/unlink
personal `ir.values`, the values with themself as
`user_id`.

Setting the default `deposit_product_id` should
therefore be done as sudo in case if the `deposit_product_id`
default value has already been created before by another user
but is no longer valid.

opw-660180

To be consistent with the needaction icon
already used in the tasks/issues kanban view

Timesheet lines are meant to have no product, and instead rely
on an implicit "Service" product. The UoM used is the company's
project UOM (project_time_mode_id), and the nominal cost of this
product is set on each employee.

Forcefully using the SO product as was done before is useless
and actually caused inconsistencies. The `unit_amount` value
would be expected in the UoM of the SO product, while still
being computed/set in the company's project UoM.

When no nominal cost can be found for an employee, the cost is
assumed to be 0, so the `amount` value is 0 too.

In addition, the product field is not supposed to be visible on
any form where timesheet lines are recorded.

This patch fixes various bits of logic related to this, including
parts which expected the `amount` value to be non-zero, or
the product to be set.

Zip range and state filtering were added at
377a6eca, but the
precedence between country, group, vat_required,
and not required were not correct.

This commit fixes the precedence as follows and adds
the corresponding tests:

 0. Explict position on partner
 1. Direct match on all criterions
 2. Match on country+zip before country+state
 3. Match on country before country group
 4. Match on `vat_required` criterion on all
    the above before trying them all again without

Where do you come from?

And reexport some missign terms