remove module_boot() usage

The problem was that when the user manipulates the graph view (in pivot
table mode), the graph view resetted the group by facet in the search
view.  It was not a problem unless a custom filter with a groupby was
already there, in which case, the group bys were duplicated.

The search view is now smarter, it only resets the additional groupbys
(and col_groupbys).   Also, to prevent usability problems, the graph
view disable the '+/-' groupbys added by a custom filters.

Note that this fix is only temporary: a revamp of custom filters, facets,
search view is coming in the next months. (at least, that's the idea). Right
now, too much 'search logic' is in the graph view.

Another note: this fix is somewhat fragile: it makes some assumptions
about the search query (mainly that the custom filter is the first facet,
also, that no other filters add groupbys/col_groupbys)

Showcase the feature by moving auth_ldap's description to README.rst

(Manual rebase of PR #1759)

[IMP] website_crm: keep the new id from the created lead to allow another function which override this one to get the new lead.

8.0 wmsstaging8 jco

[WIP] Pricelist of purchase is not in stock only and remove product_manufacturer module in view + manufacturer

[IMP] Inter-company pricing: put price on move when only partner and not connected to sale or purchase + invoice_state inverse function

[IMP] Add purchase order origin on picking

[WIP] Picking type on move for location on routing

[IMP] Provide extra function for custom buttons on picking

[IMP] Action assign optim

[IMP] Push apply should take invoice_state into account.  Propagation of cancel of stock moves should depend on procurement rule

There's a little magic inside the website enabled route modifying the
context's lang, thus breaking the logic to print the report in the
current user's lang. The direct route to display the report should
stay in website_enabled mode, as it allows to switch lang, use the
website translator and so on.

Requires an extra use_global_header to be added on
the report record, to mimic the super.create()
behavior, as super.create() is not called.

When creating a new warehouse, the linked locations should have the same company as the warehouse.
The company_id field is required on warehouse (not necessary in vals as could be added by default values) while it is not for stock.location (meaning global location, also filled with default value).

Backported from 97d99d19

When computing a field on a recordset, a subset of the records may be missing
or forbidden by access rules.  In that case, evaluate the compute method record
by record, and mark failed records as such in cache.

The <t t-raw='0'/> is already defined lower in the view (line 101)

Bootstrap's container class has a fixed width, using it in a modal
with the previous commit allowing an horizontal scrollbar makes the
layout goes crazy. Use container-fluid instead and cleaned some css.

The method onchange() executes onchange methods in cascade.  Suppose onchange()
is called and a field F=1 in the form.  If an onchange method set F=2, that
value is put in the result variable.  If another onchange method set it back to
F=1, the binding F=2 must be removed from the result variable.

Fixes #2309

Move invisible field on bottom to avoid blank space in view if display journal, group or sequence field

Those values were dropped at rev 9b343581 but
need to be forced to empty so older databases
get fixed when upgrading

Those values were dropped at rev 3b636a5d but
need to be forced back to default so older
databases get properly updated when upgrading.

[FIX] hr_recruitment: fixed computation and storage of day_open and day_close + assignment of date_open and date_closed.

At 96f038a6 product-related fields were removed due
to an important product.template/product.product
refactoring. As the field values were simply
dropped, they may not be nullified when upgrading an
existing database. Forcing them to False will take
care of it.