Steps to reproduce:
- open Discuss, open any chat, open the emoji picker (no 'Frequently used'
  emojis)
- search a term and select emojis without closing the picker (shift+click on
  desktop, plain click on mobile)
- clear the search with backspace

=> traceback: 'Cannot read properties of null (reading
`getBoundingClientRect`)' in adaptNavbar().

This happens because when we clear the search input it calls
`highlightActiveCategory()`, which sets `categoryId` to the topmost category of
the grid, which is now the 'Frequently used' category (sortId 0), added to the
picker since the emojis we just picked updated the recent state. To update the
navbar, `currentNavbarPanel` then looks for the panel holding it in
`emojiNavbarRepr`, but that representation is only built in `adaptNavbar()`,
which runs on mount and from the `ResizeObserver` only, so it was built without
the 'Frequently used' category and no panel contains it. It returns undefined,
the navbar renders empty, its size change wakes the `ResizeObserver`, and
`adaptNavbar()` crashes on querySelector('.o-Emoji').getBoundingClientRect()`.

This commit solves the issue by rendering the `recentEmojis` from a snapshot
taken when the picker is opened, so they are not added to the picker while the
while `emojiNavbarRepr` does not contain their category id.

partial backported PR: https://github.com/odoo/odoo/pull/281104

Task-[6204249](https://www.odoo.com/odoo/project/1519/tasks/6204249)



---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Issue:
----------------------------------------
When a user removes themselves as Attendance manager on the last employee on which they're set an error pops up.

Steps to reproduce:
----------------------------------------
- Connect as a user with the group `group_hr_attendance_manager`
- Install hr_attendance
- Don't be the attendance manager of any employee
- Go to an employee form, add yourself as attendance manager
- Try removing yourself as attendance manager
- Error

Cause:
----------------------------------------
When removing someone as Attendance manager, `_clean_attendance_officers()` is called to remove the group `group_hr_attendance_officer` from any user without any employee to manage.

But the field `attendance_manager_id` itself is only accessible to users with the group `group_hr_attendance_officer`. So during the `web_read` after the `write`, the user doesn't have access to the field and an access error is thrown.

Solution:
----------------------------------------
`group_hr_attendance_officer` is implied by `group_hr_attendance_manager`. So a user should never have only `group_hr_attendance_manager`.

We modify `_clean_attendance_officers()` to not remove `group_hr_attendance_officer` when the user has `group_hr_attendance_manager`.

opw-6471482