see: https://github.com/odoo/odoo/pull/179354

The  `groups_id` from `res.groups` fields have been removed and replaced by `group_ids` and `all_group_ids`.
The `users` from `res.groups` fields have been removed and replaced by `user_ids` and `all_user_ids`.

Models:
```
<res.groups>:
  implied_ids        = Many2many <res.groups> Users of this group are also implicitely part of these inherited groups
  all_implied_ids    = Many2many <res.groups> Transitive and recursive closure
  implied_by_ids     = Many2many <res.groups> Automatically added from
  all_implied_by_ids = Many2many <res.groups> Reversed transitive and recursive closure

  user_ids           = Many2many <res.users>  Users with this group specifically
  all_user_ids       = Many2many <res.users>  Users and implied users

<res.users>:
  group_ids          = Many2many <res.groups> Group added directly to this user
  all_group_ids      = Many2many <res.groups> Groups and implied groups
```

Concept:
```
The groups involved are to be interpreted as sets.
Thus we can define groups that we will call for example N, Z... such as mathematical sets.
        ┌──────────────────────────────────────────┐
        │ C  ┌──────────────────────────┐          │
        │    │ R  ┌───────────────────┐ │ ┌──────┐ |   "C"
        │    │    │ Q  ┌────────────┐ │ │ │ I    | |   "I" implied "C"
        │    │    │    │ Z  ┌─────┐ │ │ │ │      | |   "R" implied "C"
        │    │    │    │    │ N   │ │ │ │ │      │ │   "Q" implied "R"
        │    │    │    │    └─────┘ │ │ │ │      │ │   "P" implied "R"
        │    │    │    └────────────┘ │ │ │      │ │   "Z" implied "Q"
        │    │    └───────────────────┘ │ │      │ │   "N" implied "Z"
        │    │      ┌───────────────┐   │ │      │ │
        │    │      │ P             │   │ │      │ │
        │    │      └───────────────┘   │ └──────┘ │
        │    └──────────────────────────┘          │
        └──────────────────────────────────────────┘
    For example:
    * A manager group will imply a user group: all managers are users (like Z imply C);
    * A group "computer developer employee" will imply that he is an employee group, a user
      group, that he has access to the timesheet user group.... "computer developer employee"
      is therefore a set of users in the intersection of these groups. These users will
      therefore have all the rights of these groups in addition to their own access rights.
```

XML data example:
```xml
<record model="res.groups" id="group_system">
    <field name="name">Settings</field>
    <field name="implied_ids" eval="[Command.link(ref('group_erp_manager')), Command.link(ref('group_sanitize_override'))]"/>
    <field name="user_ids" eval="[Command.link(ref('base.user_root')), Command.link(ref('base.user_admin'))]"/>
</record>
```
```xml
<record model="res.groups" id="group_no_one">
    <field name="name">Technical Features</field>
    <field name="implied_by_ids" eval="[Command.link(ref('group_user')), Command.link(ref('group_system'))]"/>
</record>

or

<record model="res.groups" id="group_no_one">
    <field name="name">Technical Features</field>
</record>
<record id="group_user">
    <field name="implied_ids" eval="[Command.link(ref('group_no_one'))]"/>
</record>
<record id="group_system">
    <field name="implied_ids" eval="[Command.link(ref('group_no_one'))]"/>
</record>
```

PY example:
```py
group_helpdesk = self.env.ref('helpdesk.group_helpdesk_user')
group_export = self.env.ref('base.group_allow_export')
group_portal = self.env.ref('base.group_portal')

# we want all users having helpdesk and portal (directly or by implication).
user_portal_helpdesck = self.env['res.users'].search([('all_group_ids', 'in', group_helpdesk.id), ('all_group_ids', 'in', group_portal.id)])

# For these users we want to add access to export.
user_portal_helpdesck.group_ids += group_export

# we want all users having export
user_export = group_export.all_user_ids

# we want all users having specifically export (not by imply)
user_has_export = group_export.user_ids

```

This commits brings the following changes to Documents. Mostly UI improvements:

Keep image preview aspect ratio
==============================

Currently, images are distorted because the aspect ratio is not respected.
Images must retain their original proportions, with the addition of
horizontal or vertical spacing if necessary, so that each so that each
preview frame has the same dimensions.

Also, we want the background of the image wrapper being the same as the
body.

Add tooltip to toggle chatter btn
=================================

Add the following tooltip to the toggle chatter button: "Info & tags".

Display existing email alias in help content
===========================================

When an email alias has been configured for a given folder, and a search
on this folder returns 0 record, the helper content displayed should
include the email alias.

In case of a search on 'Home' or 'Company': no message about alias, like
for 'My Drive' or 'Shared with me'.

Also, in 'documents_details_panel':
Change labels Email Alias for Email, and Alias Tags for Tags.

Enhance Home kanban view style
==============================

Enhance the style of the file / folder group titles by turning their
h3 element into a h4*, and removing the border-bottom class.

* actually we keep the elements as they are, to avoid conflicting with
potential customizations, and reduce the police size.

Avoid scrollbar on topbar Chatter
================================

Limit the display, on large devices, of the horizontal scrollbar in the
Chatter topbar by adding 20px to the Chatter container width, and
showing the scrollbar only when the cursor is over that area.

Scroll to selected record when info panel on
===========================================

When toggling the information panel on, the space available to display
documents/folders is significantly reduced. Sometimes, the selected
document moves further down the screen and disappears from the view.

This commit makes it so the view instantly scroll to the selected
document when the info panel is toggled on.

Improve email aliases display
============================

We remove the 'Email Aliases' menu item from the 'Configuration' menu
and add an optional column in the list view to display the email aliases
(widget=email).

Also we hide the Alias Name and Domain columns. We keep the fields in
the view as they are needed for the details panel.

Hide member invite instead of disabling it
=========================================

We currently disable the member invite component in the permission panel
for users with insufficient rights (not editor) or for inactive
documents/folders.

But the restriction is not really obvious (visually) for users. We
decided to hide the invitation to members to limit their confusion.

Add database creator to highest security group
==============================================

Generally the user who creates the database receives the highest permissions
for each application, except for specific cases.

This commits follows the general logic and links 'base.user_admin' to
the 'System Administrator' group.

Fix spacing in control panel
============================

This commit aims to limit the vertical spacing between the control
panel and the menu section.

The minimum height applied to breadcrumbs to prevent vertical shift
of the view when the breadcrumbs changes dimension has been modified.
This height is defined in 'rem' rather than 'vh' to avoid affecting the
height of the control panel, particularly on high-resolution screens.

Finally, this FW port fixes a bug introduced in https://github.com/odoo/enterprise/commit/0d904521645b7001233545bab1569f1b1869ef63 using an obsolete
handler for toggling the chatter from the documents actions.

task-4444059

Forward-Port-Of: odoo/enterprise#79400
Forward-Port-Of: odoo/enterprise#77554

- Add a fallback to p2p if disconnected from the SFU while still being
in the call or after a 5 seconds timeout.
- Add logging where:
    * We obtain a track from a peer or the SFU
    * The state of the SFU connection changes
    * Our rtcSession is removed from the Odoo server
    * The peer-to-peer connections attempt connection recoveries
- Raise the default log level of peer-to-peer to `WARN`
- Add an `important` option to rtc logging so that logs that are
important are recorded even without activating the logging setting.
- Remove the generated error trade for logs as it added a lot of noise
  and the message itself should be enough.
- Add logging snapshots of p2p and sfu when disconnecting and
  downloading the logs.
- Remove the reactive session cleanup as it is redundant
with the `onDelete` of the `thread/rtcSessions` field.
- Remove `rtc.state.serverState` and put it as the `connectionState`
of `selfSession`.
- Await the peer to be ready before sending the tracks.
- Add a new p2p state "searching for network" to make it easier to know
  when the connection is stuck where we may need TURN/SFU through a
  difficult network.
- Prevent possible traceback when receiving a track for a missing
session in peer-to-peer.