pos*: point_of_sale, pos_restaurant

This commit introduces several UX enhancements in the standard POS flow:

- Removed unintended onboarding step tip.
- Updated note input dialog title to include the selected product name (e.g., “Pizza: Add Customer Note”).
- Fixed issue where the Payment button incorrectly became primary when only the order-level note was updated.
- Renamed "Order" to "Send" when only a note or message needs to be sent for preparation.
- Added "New Order" button on the Ticket screen when no orders are available.
- Improved placeholder text for floating order name input.
- Added a back button on the Floor screen in table-finding mode for direct sale.
- Moved preset filters next to order state filters (Active, Paid, etc.).
- Made the Customer button primary when a customer is required for the order.
- Removed unnecessary toaster warning for “Pay Later” payment method selection.
- Shifted order preparation warning from the Validation button to the Payment button on the Product screen.
- Added toaster notification when an order is sent for preparation summary.

Task-5116688

Related-https://github.com/odoo/enterprise/pull/97458

Currently, when a user uses the 'Set Account' button to reconcile a
statement line, the system may also create a reconciliation model
for fees for the given journal/account combination, based on the
previous statement line reference pattern.

To extract a patter from the references, the system computes the
normalised longest common substring. This will be used as regex
matching pattern of the newly created reconciliation rule.

However, the common substring may end up with '\\', which is not a valid
termination of a regex, leading to the error:
`Invalid operation. The regex is invalid.`

Steps to reproduce:

- Have an account '646000 Test Account'
- Create a Bank statement with label 'TEST REFERENCE BNK 2024'
- Set Account 646000
- Create a Bank statement with label 'TEST REFERENCE BNK.OTHER'
- Set Account 646000

Issue:

Error `Invalid operation. The regex is invalid.` will raise
blocking the action

[opw-5086638](https://www.odoo.com/odoo/project.task/5086638)
[opw-5062965](https://www.odoo.com/odoo/project.task/5062965)
[opw-5123963](https://www.odoo.com/odoo/project.task/5123963)
[opw-5166160](https://www.odoo.com/odoo/project.task//5166160)
[opw-5159871](https://www.odoo.com/odoo/project.task/5159871)
[opw-5160108](https://www.odoo.com/odoo/project.task/5160108)
[opw-5109454](https://www.odoo.com/odoo/project.task/5109454)
[opw-5086638](https://www.odoo.com/odoo/project.task/5086638)
...

Forward-Port-Of: odoo/enterprise#97865

Currently:
- when using the "Send as Message" button in a chat with an agent (opened from the systray), the default recipients are not added in the composer
- creating a default prompt for "get help on a record" on a model that does not inherit from `mail.trhead` does not work: it's the default "ask ai" chat that is opened when clicking on the "ai" button in the systray from this record's form view (
the "prompt buttons" created are not shown and the record info is not added in the prompt)
- clicking on this ai button in the systray from the res.users form view results in a crash (one tries to fetch a thread because the model has a "message_ids" field, but it's a related field and the model does not have a thread)
- "system agents" are not shown in the agent views, making it difficult to edit them (while one user could want to change the model used by a system agent if that user does not have an api key for the provider of the default model)

With this PR:
- adds the default recipients (and creates their related partner if needed, as it would be done when opening the full composer from the chatter)
- the info about the current record is always added to the context when using the ai systray button from a form view, even if there's no chatter
- the "send as message" and "log note" are added from the launch chat service, only if the model inherits from `mail.thread` (instead of relying on the field `message_ids`)
- moved the call to open the ai chat back to the form controller to avoid sending 2 events on the bus (currently systray sends an event to the form controller which in turn sends an event with the model info to the systray), and to make it easier to reuse this "open chat with agent" (shouldn't need to always go through the systray for that)
- the "system agents" are now shown in the agents views. Their name/description have therefore been reworked. The website page generator and call summarizer agents are now archived by default, as they are only used in very specific contexts

Task-5109721

### Contains the following commits:

https://github.com/odoo/o-spreadsheet/commit/1c1d1eca68 [REL] 19.0.7 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)
https://github.com/odoo/o-spreadsheet/commit/d6535bdab4 [FIX] charts: fix smart chart engine [Task: 5079093](https://www.odoo.com/odoo/2328/tasks/5079093)
https://github.com/odoo/o-spreadsheet/commit/3011482818 [PERF] evaluation: zonify evaluation [Task: 4936229](https://www.odoo.com/odoo/2328/tasks/4936229)
https://github.com/odoo/o-spreadsheet/commit/cb66cfd145 [FIX] model: ensure chart ID unicity [Task: 5153264](https://www.odoo.com/odoo/2328/tasks/5153264)

Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com>
Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com>
Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com>
Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com>
Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com>
Co-authored-by: Ronak Mukeshbhai Bharadiya <rmbh@odoo.com>
Co-authored-by: Florian Damhaut (flda) <flda@odoo.com>
Co-authored-by: Rémi Rahir (rar) <rar@odoo.com>
Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com>
Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>

#### Issue:
- Traceback when calculating the cost of a workorder

#### Step to reproduce:
- with apps: mrp, accountant
- create a MO for a product
- add a WO
- confirm
- start the WO
- Action > "Post WIP Accounting entry"

#### Current Behavior:
- get a traceback

#### Expected behaviour
- open the WIP wizard

#### Cause of the issue:
- to calculate the cost of production, wizard use all WO including the one still running. However as it is still running its end date is registered as `False`. It raises a traceback when it compares the end of the WO with a limit date because `bool` and `datetime.datetime` are not compatible for '<'.

#### Solution:
- check if the end date of the WO is defined


In module mrp_workorder an override of [button_start](https://github.com/odoo/enterprise/blob/18.0/mrp_workorder/models/mrp_workorder.py#L284-L295) change how work order are launched. Therefore, the test should be launched on an Enterprise run.

opw-4961873

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

Forward-Port-Of: odoo/odoo#232758
Forward-Port-Of: odoo/odoo#221938

**Steps to reproduce:**
- Make a sub category, such as Soda for Drinks in PoS product categories
- Make a product and assign this sub category to it
- Allow the category in the PoS configuration for a Mobile order Session
- Open the Session, the product will not be displayed

**Problem:**
When a product has a subcategory, it is not displayed in the mobile interface, even if said category is allowed in the settings.
This problem does not occur in the Kiosk, only on the mobile sessions.

**Why the fix:**
The products should be displayed if their category has been added to the available categories in the settings. It now works as it does in the PoS and the Kiosk, meaning it is displayed as long as the sub category is mentioned in the Restrict Categories section of the configuration.

Also, in case you have categories A -> A/B -> A/B/C and you don't have products associated to A but you have some in C,
they won't show up in the self.

Currently, products from child categories can be shown in the self when all their parent categories had products associated to them.

When computing the available categories, we would only return categories which had products directly related to them, regardless if their nth child had some. Thus in the setting mentioned previously, only the category C was returned.

However this logic is not correct with the fact that the self, not in kiosk mode, only shows the top categories, meaning only the categories without parents. 
https://github.com/odoo/odoo/blob/434e8cf53a039cc2efc3cb531608028182928ad9/addons/pos_self_order/static/src/app/pages/product_list_page/product_list_page.js#L146-L151

The self was not showing the products from C as C had a parent category. In order for the product from C to be shown, the category A had to be included in the list of available categories.

opw-4934728

Forward-Port-Of: odoo/odoo#221740

Scenario to reproduce from 18.0:

- install right-to-left (eg. arabic) language on website
- open a portal record with chatter (eg. /my/invoices/1)
- switch to right-to-left language
- scroll horizontally to the left

Result: there is a huge amount of whitespace scrollable to the left.

Cause:

In 18.0, the chatter has an hidden textarea .o-mail-Composer-fake with
position "left: -10000px; top: -10000px;".

But the chatter assets (portal.assets_chatter_style) are called
dynamically with getBundle which is using the session lang instead of
the website lang.

So the bundle is gotten with the wrong lang and the CSS is not rtlcss'ed
and this create big whitespace to the left of the page.

Fix: set the website request language when getting bundle for the
frontend.

Note: this PR also create a TestLangUrlCommon to prevent TestLangUrl
tests of being run a second time in TestControllerRedirect.

opw-5013485

Forward-Port-Of: odoo/odoo#232759
Forward-Port-Of: odoo/odoo#223575