Steps to reproduce:

- Enter website edit mode.
- In the right panel, click on the "Intro" category.
- Enter "quotes" in the "Search" input of the modal.
- Click on one of the two "quotes carousel" blocks.
- After the "quotes carousel" block is inserted on the page, click on its "Blockquote".
- Click the red "delete" button that appears above the "Blockquote".
- Bug: The carousel item is removed, and only the arrows to move the slide are shown on the screen. If you click on one of the arrows, a traceback will occur.

The exact same bug was previously fixed in commit [1], but since the modification of the "carousel quotes" snippet in commit [2], the fix no longer works.

There is a system that removes the parent of a snippet that gets deleted if this parent is empty after the deletion. This allows, for example, to remove a column if its content is emptied to avoid leaving an empty column on the page.

An exception to this rule was introduced by commit [1] for carousel items. Indeed, we don't want to remove a carousel item when it is empty.

This exception checks if the grandparent of the deleted element is a carousel item. It worked initially because when the content of a slide was deleted, the container still remained within the carousel item. But this is no longer the case for the "quotes" carousel since commit [2], where the intermediate "container" element is no longer present.

This commit also adds steps to the "carousel_content_removal" tour to prevent the issue from reappearing.

[1]: https://github.com/odoo/odoo/commit/3c194faa930b0d3a537ca8b893b2c0442b5464e7
[2]: https://github.com/odoo/odoo/commit/4357ce81ed89bd389eafe3756733758736bad6cb

opw-4417366
opw-4395645

Steps to reproduce the bug:

- Go to the website edit mode.
- Drag and drop a "Text - Image" block onto the page.
- Drag and drop a "Media List" block at the bottom of the page.
- Drag and drop a "Text" block at the bottom of the page.
- Click on the "Text" block.
- In the "Text" block options, click the "Create a link to target this section" button.
- Click on the "Button" inside the "Text - Image" block.
- In the options, paste the "link" to the anchor copied to the clipboard into the URL input of the button.
- In the "Column" options, add an "On Scroll" animation to the column.
- Save the page.
- Click the "Text - Image" button.
- Bug: the page doesn't scroll to the "Text" block.

This bug was introduced by commit [1], where the "overflow-x: hidden" CSS rule, used to prevent a horizontal scrollbar during animations caused by overflowing content on the right side of the page, was moved from the HTML element to the body element.

The bug appeared because when the code triggering the scroll animation to the anchor runs after clicking the button, it checks which element is scrollable. At that moment, the body has "overflow-x: hidden," which causes its "overflow-y" to become "auto" instead of "visible" (browser behavior, see https://developer.mozilla.org/en-US/docs/Web/CSS/overflow). The body element is then considered scrollable, even though it isn't. This is why the scroll animation doesn't work.

To fix this, we replace "overflow-x: hidden" with "overflow-x: clip". This is more appropriate in this context and prevents "overflow-y" from becoming "auto".

We also add "display: flow-root;" in combination with "overflow: clip" because without it, "overflow: clip" alone may not be sufficient to prevent elements inside "body" from overflowing, particularly animated elements in Firefox.
This creates a new formatting context, preventing unexpected overflow behavior across different browsers.

[1]: https://github.com/odoo/odoo/commit/fece9cb85761e6cb3fe3642f947661464402363b

opw-4393527

This error occurs when a product is added to one table, and the payment screen is accessed where an online payment method is selected but the payment is not completed. Subsequently, switching to another table and attempting to make an online payment results in the issue.

Steps to reproduce:
---
- Install ``pos_online_payment`` and ``pos_restaurant`` module
- Create a new online payment in ``Payment Method(eg: Test)``
- In Configuration/Settings, add it for a restaurant in ``Payment Method``
- Now open a session in a restaurant > Select one table > Add products > Order > Payment > Click on Test
- Click on ``+`` > Add product > Payment
- Click on Test and Validate

Traceback:
---
``Expected singleton: pos.order('p', 'o', 's', '.', 'o', 'r', 'd', 'e', 'r', '_', '2')``

Previous Behaviour:
---
When an online payment is selected for the first table but exited without completing the transaction, an RPC error occurs, causing the system to switch to offline mode. Consequently, the order encounters an error when attempting to place an order and process an online payment at the second table. At that time, it creates a new order as ID ``pos.order_2`` and updates the previous order. Due to what we get ID like ``pos.order_2``, leading to the issue.

After Commit:
---
When creating a new order for another table at [1], the ``online_account_payment_id`` is set to false. If this value is false, we will assign an empty set to ``online_account_payments_by_pm[pm_id]``.

sentry-5703437687

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

### Description of the issue/feature this PR addresses:

This error could be raised if oAuth session has expired before Odoo gets a chance to close the IMAP connection:

```
<class 'imaplib.IMAP4.abort'>: \"socket error: [Errno 32] Broken pipe\" while evaluating\n'model._fetch_mails()
```

We get this error from time to time when fetching emails from a Gmail account configured with Google oAuth.

### Current behavior before PR:

Fetchmail scheduled action hangs when this happens, and no email are fetched anymore (dangling connection still in worker process, until this worker is recycled? Is it possible?).

### Desired behavior after PR is merged:

Catch properly the exception and have a scheduled action terminating nicely.

We did this patch on v14, but we are not entirely sure it is fixing the encountered issue as this happened randomly, and very rarely.
But I guess it is anyway a good thing to catch such errors to get a WARNING log, like it has been done by catching `OSError` for timeout issues.

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