* Number of emails should not take into account internal notifications
 * Remove Channel and Tasks from issue report as those are not really
   used anymore
 * Remove New filter as it can be done through stage filtering instead
   of using a not obvious heuristic based on stage sequence

A new view is dedicated for that kanban view. It is based on the standard
issue kanban view but using the group_create=false attribute to disable
the ability to create new columns.

It is done using a different view because standard issue kanban view
requires this ability. However it is not possible to achieve that goal
using conditional attributes.

New API migration of project issue was not correctly done considering
module organization. This commit reorder files according to the
guidelines.

The test is never started and the tour is not up to date so remove it
from the DOM until it is converted to new tour system.

in "Website Admin" settings pricelist groups were not updated because they were
not declared in the view. added now.

Also added group to pricelists menu and fix typos.

rename options, add radio widget

installing a theme redirects to the website instead of the backend menu.

Using a safe_eval is overkill and can nicely be replaced by operator

Closes #13138

+ hparfr

Several modules defines records with the external ID `base.foo_bar` while it is
created inside this module (typically menus and groups).
While there is no technical reasons to do so but this may introduce issues:

- these records will not be deleted during uninstall
- if a language is loaded before the installation of the module, it won't be
  translated

The uninstallation will only remove the records with an external id linked to
this module (these would only be removed when removing base).

Installing a language before the module will drop the translations not linked
to an existing external id (as it can not be resolved).

This commit correct all the external ids tagged as from base or other incorrect
modules.

hr_gamification should be adding hr groups to the security of gamification.
Creating the group base.group_hr_manager in gamification in case hr is not
installed is confusing and redundant with existing manager groups.

Creating a external id in a different module than the one where the record is
declared is a bad practice.
Setting a correct module is both important for a correct uninstallation of the
module (which uses the module to decide which records to remove) and for the
translations (records tagged with 'base' module needs to be declared in the
base.pot file).

one2many, many2many, text and html fields should take all space in a form view
for a better rendering instead of taking only 2 col or not having the label in
front the field.

When a model has no form defined, a default view is generated displaying all
fields of the model.
The one2many and many2many fields were not displayed on the form, probably for
aesthetic or historical (2008) reasons.

The snippet section can have a color or a background. Previous commit
added the functionnality for its innercolumn too... but having a bg
image on top of another one does not make sense, so only keep the
color option for columns.

- s_references
    * Replace demo images (lighter ones)
    * Move title to left
    * Review responsiveness
- s_big_message
    * Add background
    * Use grid system

* Replace demo blog post covers
* Add xml ID to demo images so they can be easily replaced by themes
* Remove unused images

In the merge partner wizard, there's a button in the footer which
trigger the method `action_close`. This method is decorated by
an api.multi and begins with an ensure_one() and if you click
on close directly after opening the wizard, self.ensure_one
fails.

The thing is, `action_close` only return an ir.action.act_window_close
action and there's a special attribue you can set in the form
view button to make it return an ir.action.act_window_close directly.
If we use this technique, then there's no traceback anymore. So this
is the fix.