[FIX] logging PostgreSQLHandler: expand message + use contextmanagers to handle exceptions and cursor

Extended view inheritance

[FIX] Fix o2m record duplication when clicking on a button

The button action will execute a write call, creating the new line.
The reload is necessary to avoid recreating the line when using the save button.

Revert "Merge pull request #225 from odoo-dev/master-frontend-assets"

This reverts commit dd900408, reversing
changes made to 4da882d4.

Commit backported from master 8ad97da8

[CLEAN] website_mail: cleaned a lost console.log and a commented line that should have been removed with pr 213

[FIX] website_sale, website_event_sale: updated JS tests according to the new dom of the checkout page introduced in pull request 232

[FIX]t-field wrong outputs when precision is 0

[FIX] website_sale, website_event_sale: updated tests according to the new dom of the checkout page introduced in pull request 232

[FIX] mass_mailing: fixes in mail (default recipients), mass_mailing (recipients computation), web (chardomain widget)

[FIX] mail: fixed get_default_recipient, trying to call a method even if the target model do not have it; also fixed default recipients generation on the contact model; sending a mass mailing when not having recipient now raise a warning.

[FIX] web: chardomain widget: fixed selection of some records in a list (bad domain formatting), fixed domain evaluation tah is done server-side instead of through a stringigy.

Before this commit, @mode=primary would be sorta-ignored[0] if the current
view and its parent had the same model: the current view would *still* get
applied (as an extension) when asking OpenERP for its parent. This commit
makes mode=primary views behave regularly, they are *never* applied when
asking for their parent, only when asking for them or their children.

This allows "forking" views, and using extended views in some contexts without
breaking or duplicating the original view

[0] there was actually a problem when asking for the current view directly,
    first its parent would be resolved by applying it, then it would be
    applied to resolve itself, the view would thus get applied twice (oops)

[IMP] website_sale: correctly submit the payment form using a post request, correctly create the tx asynchronously

not sure that's actually useful, and can still go always -> enabled -> disabled...

Also add a few comments to note understanding of code

rco notes that group tests are generally intersections, if the user has *any*
group set on the object he can see/use it. This change is a literal
translation of the original semantics, which may be wrong.

just forwarding the context object does not count as using it, if callees want
a context they can ensure they've got one on their own

[IMP] don't pointlessly recreate view_obj every time _views_get is called, better use of pool & data APIs

should probably validate that there's an inherit_id (?)