[FIX] orm: do not drop foreign keys of transient models

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.
[FIX] sale: backport of rev 709e22c32aca

[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
[FIX] portal_sale: security rules matching the one of public user

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] payment: access rights limitation

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.
[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.
[FIX] auth_ldap: avoid to try twice the authentication to the ldap server

See #1982
[FIX] payment_paypal: create account with at least required fields
[FIX] payment_paypal: paypal account migration: correct search of existing providers
[IMP] payment: simplify rev d99835e

The group public is defined in base so no need to add security rule in website_payment module (same as for portal)
[FIX] website_sale: retrieve transactions as superuser

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.
Forward port of branch saas-3 up to rev 2ee1843
[IMP] website_sale: do not show transaction on sale order

This object is quite technical and has not purpose to be displayed on a sale order.
[FIX] orm write: do not try to store computed & stored fields for relational records deleted by *2many fields

opw-613772
[MERGE] forward port of branch 7.0 up to f5f7609
[FIX] loading: always process auto-installed modules for new databases

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
[MERGE] Forward-port 7.0 up to 938502a
[MERGE] Forward-port saas-3 up to 09ab2d4
[FIX] orm: typo during forward port 60a82133cc0e0d7c4879b6c518054cbd44e20c0c
[MERGE] forward port of branch saas-3 up to b6e6b57
[FIX] purchase: keep reference to purchase order line

When generating an invoice from a stock.picking, the reference to the purchase.order.line needs to be kept (e.g. this is needed by anglo-saxon for price valuation). (opw 600767)