`@groups` attribute in qweb views

[MOV] [RENAME] project_mrp -> sale_service

[FIX] project_mrp: fixed with in which product attributes are added, probably due to product and template refactoring

[IMP] add XID to view name in Ace editor dropdown

* Looks better
* Allows for a label
* Allows for longer template names and ids without cutting off
* Room to grow more info bits

Make attachment data available under public by default

Qweb foreach

Fix postprocessing of request arguments in website

[IMP] hr_timesheet, hr_timesheet_sheet: merge timesheet and hr_timesheet reports; base report moved to hr_timesheet; hr_timesheet_sheet adds data to the report using inheritance.

[ADD] support for multiple value query args in keep_query()

[REF] website: change URL to new Odoo website

Assuming access rights are correctly configured, this allows providing
downloads for any attachment type, not just to display images via
/website/image.

TODO: unify attachment querying, we've got stuff over both web/ and website/

[FIX] sitemap does not show pages (Fixes #452)

the /page/ controller was not using the page converter

the /page/ controller was not using the ``page`` converter

The @groups attribute in qweb views was not rendered (even when matched by the
user), so editing a template with an @groups would either remove the whole
section (if the user didn't have the groups, fixed in previous commit) or only
removed the attribute itself making it visible to everybody (which ought be
fixed-ish by this commit).

If the current view uses @groups attributes (possibly in called templates),
the corresponding elements are rendered to a void (empty string in qweb). If
said user can edit the page, does so and saves a view section in which there's
a @groups to which he has no access, the element[@groups] is completely
removed from the template once saved, losing it.

If QWeb encounters an @groups to which the current user has no right during
rendering, have it request a no-RTE page, so the user can not RTE-edit the
page (or drop snippets in it).

[ADD] website_instantclick module: using instantclick lib, faster loading of website in public mode. Done in a separate module to avoid doing it by default.

[IMP] crm: onchange partner on lead form view better fills partner and contact name, depending on whether the partner is a company or not

[IMP] product: all left menu item became product.template's action

[FIX] website: clean for save of snippet editor don't remove conteneteditable attributes

[IMP] claim: add a placeholder on resolution in form view

[FIX] new style for default form views

Added standard and Schedule-vi chart with taxes
removed private and public chart with taxes files

[FIX] issues when uninstalling modules: unlink ir.action.todo which are related to actions which will be deleted (fix issues when uninstalling modules) + check for menu existence before displaying need action

[FIX] graph/pivot tables: remove non stored fields from available measures

If website is installed but not used/enabled for the current controller,
overridden methods like _get_converters will *still run* for the controller's
dispatch.

This means a ModelConverter used in a controller with website installed but
not enabled will use website.models.ir_http.ModelConverter, not
base.ir.ir_http.ModelConverter, and base's args postprocessing will *not* be
able to convert the placeholder object to a real UID, only website's
postprocessing can do so.

And as far as I can see there's no reason to skip the URL building validation
either, only the multilang stuff relies on and requires that the controller be
website enabled (and in fact that it be multilang enabled), so only *that*
should be gated behind a flag.

Also always call super(), there's no reason not to and others might add args
to postprocess on base rather than website, ending up after website in the
MRO.