[IMP] work on inline search view in web client

incomplete work.  So far, the search view widget has been split in
two widgets: SearchView and SearchViewDrawer.  The SearchViewDrawer
has been inserted inline, and some preliminary work has been done
to improve the layout.
[FIX] add support for default filters in search view

support for default filters was broken in the previous commit,
now it works again.
[IMP] lots of layout work for inline search view (addon web)

mainly to correctly style the custom filters list.
[IMP] hide drawer when switching views (addon web)

the drawer wasn't closed when switching views, which might be a
problem when the user switches to a form view.  Also, renames the
variable 'searchview_drawer' to 'drawer'.
[FIX] correctly display the searchview/drawer (addon web)

the searchview has been splitted in two widgets: SearchView and
SearchViewDrawer.  They are dependent of each other, so a drawer
has to be created for each searchview.  This was not the case in
some form views (inline, created by a wizard).
[FIX] remove an extra border-bottom css rule (addon web)

the border-bottom was set on drawer_container and on drawer,
resulting in a double border.
[IMP] unlink ir.action.todo which are related to actions which will be deleted.
[IMP] better architecture for searchview/drawer

Before, the searchview and the searchview drawer had to be instantiated by
the user and appended separately to their correct place.  Now, the
searchview is responsible for creating/destroying the drawer, and the
user is responsible for correctly using the insert method with
the node where the searchview/drawer are to be inserted.
[FIX] fix the graphview field selection

searchview has been split in two parts, and the inputs are now located
in the drawer
[IMP] improvements to inline searchview (web)

this commit splits the widget CustomFilters in two widgets:
CustomReports and SaveFilter.  CustomReports is the widget
displaying the list of reports, and SaveFilter obviously is the
Save Current Filter widget.

The goal was to put the custom reports in the first column and the
Save Current Filter form in the second.
[FIX] correctly loads default filters (addon web)

also, hide/show the custom reports list when it is empty/non empty
[IMP] improves searchview appendTo

after some thought, the extra method insert was not really necessary.
It was at first a way to force the user to give two nodes to determine
where the searchview and the drawer were to be inserted.  However,
the second node can be omitted, a perfectly reasonable default is
to append the drawer just after the searchview.

Then, the role of insert is exactly the same as appendTo, so it makes
sense to override appendTo and remove insert.  Simpler, and the job is done.
[FIX] update the searchview tests

to accomodate the fact that the searchview has been changed.
Two changes need to be accounted:
(1) the drawer html structure has changed (oe_selected class is
replaced by badge, some li tags are replaced by spans, ...) and
(2) the CustomFilters has been split into CustomReports and
SaveFilter, so there is an extra filter in the drawer inputs.

Also, the searchview need a parent to react to the switch_mode event,
so the tests add a fake parent to the view in make_search_view
[IMP] replace all 'Group By...' by 'Group By'

in all searchview, the 'Group By...' looks weird, next to the Custom
Reports and Filters.  This change was requested by the upper management
[IMP] work on scrollable zone in web client

add a div parent to oe_view_manager_body, and move the searchview
drawer inside oe_view_manager_body.  This is in preparation to the
goal of making the oe_view_manager_body div scrollable
[IMP] slightly improve the html structure

of web client: remove an useless div .oe_view_manager_parent
introduced by a clueless developper.
[IMP] change scrollable area to main view

Now, only the main view is supposed to scroll (the part below the
header with the view selector).  The left menu, top bar and header
are supposed to stay fixed.  This is done by carefully using
position:relative and absolute.  However, this is likely to
introduce some (many?) issues, perhaps with tooltips position and
such.  The bug hunt is on!
[IMP] small css tweaks

correct a few problems introduced by the change to the scrolling area.

Note: body is in overflow:auto to allow scrolling when there is no view
manager (for example, client action)
[IMP] fix a css problem with multiple view_manager

when a view_manager is contained inside another, the
css rule for defining a scrollable zone (with position:absolute)
was also applied to the inside view manager.
[FIX] various css fixes related to scrolling

(1) it seems that position:relative behaviour is undefined in a td,
so it has been moved to the div below oe_application
(2) the left menu bar can now scroll vertically if necessary.