deprecated use oauth2 instead

- Remove domain (only search context)
- Set correct default values for both template and variant when creating a bom
  when coming from a product variant from

- Reorder views per model and per actions
- Remove dead views and actions
- Flatten configuration menu, only the resource submenu is kept
- Rename mrp_bom_tree_view to mrp_bom_line_tree_view (no other xmlids where harmed in this commit)
- Add a view mrp_bom_tree_view for bom list with name and product variant when group_product_variant is enabled

[IMP] Creation  date is confusing since its not the creation date in order point with po lead times. And user want the scheduled date rather than the creation one

[FIX] Scheduling of orderpoint: it was wrong to add the supplier lead time at every rocurment (what do you do if you manufature) and wrong for PO: you were always late

This causes issues when people delete the Website Sales team. The
website_sale module already adds a salesteam_id to website, which is
configurable. So instead set that to website.salesteam_website_sales by
default and use it in both website_sale and website_crm.

Before this request.registry.get('ir.model.data').get_object_reference()
was used to grab the event_sale.product_product_event record. After
deletion of this product get_object_reference() would still return the
old id, which upon usage would throw a MissingError exception.

So to fix this, bypass the registry caches by using just
request.env.ref().

Try to protect users from locking themselves out.

Unactivating the preferred language of a user will prevent him from
logging in.

When creating an automated action the filters created for them showed up
in everyone's search box, which often times was confusing and not really
useful.

The methods for getting the quants took a lot of parameters,
as in most of the cases (only exception being the negative
quants reconcile) the parameters depended on the move/pack operation
being processed.  By just passing the move and ops the code gets simpler.

There should also only be one place where most of the domain for searching the quants
based on the move/ops is calculated.

- Google sync was dropped with new design
- Use new API alert/confirm dialogs
- The user was able to click on the button... by clicking next to it
    (remove the button template, create it in JS)
- Fix some exceptions in routes
- Convert CSS to LESS
- Update google tutorial

(google_calendar module needs some improvments, especially to give
meaningful error messages to the user when the google server sends
back errors)

- Contact filters were dropped with the new design
- The 'me' filter was not working correctly (wrong colors)
- Remove some useless/unnecessary code
- Use new API confirm dialogs
- Convert CSS to LESS

Since rev. 16eb36ff, do_show() and do_hide() on widgets toggle the classname
o_hidden on which the rule 'display: none' is defined, instead of calling
jQuery's show() and hide().

The method do_toggle(), sharing the same logic, has been introduced in rev.
74c5f772.

From now on, every widgets should call do_toggle() instead of $el.toggle() as
it will have undesiderable effects (they should call do_show() and do_hide()
instead of $el.show() and $el.hide() as well, this as been done in 16eb36ff).

This rev. replaces all calls to $el.toggle() by do_toggle(). It also adds
an optional argument to do_toggle() to force hidding or showing the widget.

When clicking on the breadcrumb to come back to a previously loaded action, the
restore() function is called. With this rev, this old action is shown only once
the Deferred returned by the optional on_reverse_breadcrumb callback is
resolved, i.e. when the action is ready, as it should be.

Add "Alert" and "Confirmation" as default titles for
alert and confirm dialogs

When a location is marked as return location,
upon a return it can be put it in the possible return locations,
when it is in the same warehouse or under the same parent location.

The push rules are also applied on returned moves now, but
only when the push rule does not return the return to the original location

The lot in the return line is removed as it does not make sense
(better to change it on the pack operations)
and the views are cleaned

The returned picking is also automatically reserved.

can lead to issues when trying to compute followers.

This case appears in the onchange mechanism. Indeed it may
manipulate temporary and/or new records, not having an
ID. In this case the computation of followers is not
necessary anymore.

as there is no more column sharing anymore. This ease the use of the
application by having a lightweight data to customize.

[IMP] account: changed the displayed field of the taxes in the invoice reports, it is now the description, i.e. 'label on invoices'. Based on a request from fp.

Add rules so that the enterprise version div.o_checkbox does not
break community layout

- Use the ControlPanelMixin in the Import view;
- Adapt the stylesheet to fit with both community and enterprise editions;
- Convert the css into less, use mixins and variables defined in web;
- Return the reload() deferred in the on_reverse_breadcrumb callback so that the
  previous action waits to be properly reloaded before being shown.

Adapt the template according to the refactoring of the parent commit.

Refactoring of the DOM structure and classnames of the list view's action
buttons (in the control panel), for new design compatibility. This refactoring
was required as some addons shared between both editions (e.g. base_import)
define their own buttons and extend the ListView.buttons template to insert
them.

this way we can style the div and use the trick to have the child of a
flex-item filling 100% of its parent (flex item in relative position and
flex child in an absolute position). It is needed to have a consistent
look betwenn Odoo enterprise and Odoo community.

code moved from the deprecated hr_recruitment_document

The feature will be readded in hr_recruitment

Showing only the taxes from the same company. Beware that multi-company as
adminstrator is not supported, anyawy this mitigate some of the possible errors
if it happens anyway.

Only allow it when there is an inverse many2one. This is meant to try
and prevent users from messing up their database.

This is to avoid users accidentally breaking inventory values.

The global event variable is magically ok on some browsers
but not on firefox

(Thanks aab)

Bug introduced during previous forward-port