Steps to reproduce:
-------------------
1. Enable "Automatic Receipt Printing" so the receipt is auto printed after paying an order
2. From PoS, make an order, select it to invoice, and click the pay button.
3. While loading (normally a few seconds to finish the invoice), switch the tab and stay there for few seconds (the time the invoicing has finsihed).
4. Come back to the initial page, a traceback will appear and the ticket is not printed.

Why it happens:
---------------
The receipt is printed when the parent of the `OrderReceipt`, i.e. `RenderContainer` is rendered. In this case, we assume that `OrderReceipt` has already had the time to be mounted and thus it's in the DOM, so in this case, `this.ref?.el?.firstElementChild` has the order receipt. However, when switching the tab, and since OWL uses `requestAnimationFrame` as a scheduler, and since the browser will throttle `requestAnimationFrame` when the tab is not active, we will not have access to the order receipt component in its parent's `onRendered`!

The fix
-------
Instead of seeing the parent renders as a sign that its child has been successfully put in the DOM, we now renders the child component (OrderReceipt) in its own container and thus we can hook into its `onMounted` lifecycle where we know for sure that this component has been successfully mounted and attached to the DOM, and can be accessed through `this.ref?.el?.firstElementChild`.

opw-5124585

Forward-Port-Of: odoo/odoo#241781
Forward-Port-Of: odoo/odoo#239008

Steps to reproduce
===================
1. Go to Forum.
2. Select any forum and Click on New Post.
3. Add a title and keep description empty.
4. Post Your Question.
=> The title is marked as invalid.
5. Now add a description.
6. Post Your Question.
=> Error page: Bad Request
7. Go back or open any forum page
=> Will receive error on each page until you clear sessionStorage

Technical
============
The commit [1] updates the website forum interaction to use
the html_editor `Wysiwyg` instead of `loadWysiwygFromTextarea`.
The textarea is hidden and populated through `WebsiteForumWysiwyg`.

When the description is left empty and the form is submitted,
`WebsiteForumWysiwyg.onSubmitButtonClick` populates empty content
into the textarea, sets the `readyToSubmit` property to true, and
resubmits the form to trigger the interaction logic. The editor
container is then validated as empty, marked invalid, and the
submission is prevented.

After the description is refilled and the form is submitted again,
the `readyToSubmit` is already true, causing an early return from
`onSubmitButtonClick`. This skips populating the textarea from the
editor container. Since validation is performed against the editor
container, the form is submitted successfully.

As we use form action that relies on named inputs, including the hidden
textarea, the submitted payload contains an empty textarea value.
As a result, the request fails with a bad request error due to empty content.

[1] https://github.com/odoo/odoo/commit/6bd3d1b557f82475f0a78ef8ff0529528e5f2b29

After this commit
======================

This commit fix the issue by resetting `readyToSubmit` property to false.

Task-5400394

Forward-Port-Of: odoo/odoo#241544

**Description of the issue this PR addresses:**
------------------------------------------------
In non-aside chatter, the **Jump to Present** action did not work reliably. When users clicked it, the view flickered and the scroll position jumped back, preventing users from reaching the latest message.

This happened because the browser’s native scroll anchoring interfered with the scroll-to-bottom behavior when messages were reloaded.

**Current behavior before PR:**
---------------------------------
- In non-aside chatter, clicking **Jump to Present** caused flickering.
- The view jumped back instead of staying on the latest message.
- Users could not reliably reach the most recent messages.

**Desired behavior after PR is merged:**
-----------------------------------------
- Clicking **Jump to Present** in non-aside chatter scrolls directly to the
  latest message without flickering.
- The scroll position remains stable and does not jump back.
- The **Jump to Present** button works consistently.

**Task:** 5264332

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

Forward-Port-Of: odoo/odoo#240934