If the server was started without -i or -u and
happened to initialize a fresh database,
auto-installed modules that depend
on `base` only would stay in status "to install"
without actually being installed (until the next
installation round was triggered).
This was of little consequence in 7.0, but causes
a crash in 8.0.

Fixes #953

[FIX] orm write: do not try to store computed & stored fields for relational records deleted by *2many fields

opw-613772

This object is quite technical and has not purpose to be displayed on a sale order.

Due to additional security rules, the transactions made as public user will have a new partner_id. The transaction needs to be retrieved as admin to be set in the context.
The operations in payment_get_status are made as superuser but the session_id is checked in the assert above to avoid url manipulation.

The group public is defined in base so no need to add security rule in website_payment module (same as for portal)

See #1982

[FIX] point_of_sale: set journal as pos payment method on setting journal in the payment methods of a pos config when none is set.

Do not allow everybody to access account.transactions.
Restrict by default to readonly and even restrict the access with a record rule, give access to salesman.

The portal users had no access to the attributes objects (while the public user does) and was not allowed to render the shop page.
Fixes #1961

[FIX] sale: sale report view, wrong domain

Quotations are sale.order with state draft and sent
Sale orders are sale.order with state other than draft, sent and cancel

During the update of a module, the existing foreign keys are dropped if they have a different ondelete_rule than the one specified on the field.
The foreign keys for many2one transiant -> non-transiant are created with cascade rule by default (see `m2o_add_foreign_key_checked` method) so the check needs to be realised in the same conditions.

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

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

PR #720

In this awesome programming language called javascript, undefined is neither bigger nor smaller than a string. Previous code was then considering undefined values equal to any string.
This fix allows to sort in a column of a o2m field and group the undefined values together. opw 607704

The wizard 'Edit Survey' > 'Add Question' was trowing an access rights error as the id was passed as a string instead of a real id. opw 607854

The tax_amount field should contain the basic amount (without tax) for base tax code. (opw 613470)

When sending an email, both formats 'Name <email>' or '"Name" <email>' can be used for fields 'From', 'To' and others. If the name contains unicode characters, a regex only matching '"Name" <email>' was used to encode the name with RFC2047. That meant that the name was not encoded and eventually dropped, using only the email part.
Instead of using a limited regex, use the parseaddr method from email library.
Fixes lp:1272610, opw 607683

as ir.config.parameter has limited access