Fixes issue #1755 partially, when the new term
will be translated

As the whitespace is stripped when exporting terms
to translate, it must be done as well when matching
translations at runtime.

Fixes issue #1755 partly

The changes for QWeb template translation have introduced
res_id values in PO comments for all `#: view:` terms, as
the real database id needs to be resolved when loading them.

For non-QWeb views this is not necessary and actually caused
the terms to be dropped when the res_id could not be resolved.

Rather than having a different PO comment format for QWeb and
non-QWeb views, we can extend the QWeb hack to force the
res_id to 0 for non-QWeb views.

Fixes issue #1755

Distributing our version of pyPdf is not required anymore since we
introduced the new reporting tool.

In order to keep reports working, the standard python library
`python-pypdf` has to be installed instead (through pip or your
distribution's package manager)

[FIX] account: account_invoice's onchange_partner_id uses the first partner bank account if several are defined. Merge of #2280

Recently, the graph view was changed to prevent changing groupbys
for active custom filters.  Unfortunately, I did not take into account
the fact that pivot table can be drawn in part when expanding rows.

The "frozen" parameter was then undefined and caused display problems,
this patch should fix the issue.

The method was expecting that name_get() returns complete and in-order values.
Because of this, some records in the recordset could end up without a value.

[FIX] website_hr_recruitment: add param to force all countries else it use GeoIP, check that country returned by GeoIP have jobs availables else fallback on all countries

This feature hasn't been implemented because of complexity problems.
Therefore, we should not allow the developer to use it.

[FIX] website_sale: The product breadcrumbs in shop not working.

Well actually it's an empty forward port to avoid forward porting last 7.0 commit in saas...

Fixing breadcrumb not being displayed after some action button (e.g. validate invoice, opw 612763)

[FIX] orm: correct read_group() on models with `_group_by_full` (introduced by previous forward-port)

also add tests of `_group_by_full` functionality

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)

[FIX] website_event_sale: remove invalid code chunk introduced during previous forward-port (56f2b7ae0f6)