Currently, if users try to send invoices / quotations / purchase orders to
themselves in order to look at final result, they can't do so because our
default chatter protection prevents sending mails to authors themselves.

This commit uses 'mail_notify_author' context key and allows users to send
mails from the header buttons available on SO / PO / invoices to themselves
if they are in recipients.

This commit targets only those buttons as this is the main case where we
want to allow people to send emails to themselves. In order to avoid
side effects no other use case is supported.

Task ID-2294130

closes odoo/odoo#55809

X-original-commit: 09918f320ba712b0bd90a6852825fad864655b04
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

This reverts commit 99f497b390e680629dce3a7e2e282ada74ee9884.

No code changes, simply move them to the right places,
the place where they should be.
This will ease the split between stock and purchase
addons.

The reified view on the res users will be dropped in the following commit.

The previous commit adds support to define each group as a computed field on the res users.

This commit defines:
- A boolean field for each 'isolated' res.group, i.e. a group in the hidden category.
- A selection field for each 'Application' res.group, i.e. a group in a application category.

Example:
- The group to manage pricelist in sales becomes a boolean field
- The groups project user/manager become a selection field

This adds the possibilty to select another account.invoice object in a vendor bill or credit note, to automatically copy its lines.

When the purchase app is installed, the same field can be used for auto-completion and users can choose between vendor bills or purchase orders (preferably PO)

Co-authored-by: dat@openerp.com

Purpose
=======

Steps :
- Blank DB (without demo)
- Install inventory, Sales
- Create some products + update qty + activate serial number from setting and create some products (I tried this step and faced traceback)
- Now try to install Purchase app
It gives traceback..

Specification
=============

As the field po_lock is defined on the res_company and a related field is defined on the res_config_settings.py file, modify the import order.

change the position of res.company file, so that fields of po_lock will define first and then it will not generate field's error in res.config.settings file.

Now that we only have one model (res.config.settings). Uniformize everything according to the guidelines.