Problem:
The abandoned cart reminder can crash when Click & Collect is enabled. The stock availability check reaches website_sale_collect._get_product_available_qty(), which assumes request.cart always exists.

Solution:
Safely access the cart with hasattr and fall back to the existing no-cart behavior when it is unavailable.

Why:
Scheduled actions may have a request object without a frontend cart. This fix prevents the cron from failing while sending abandoned cart reminders.

Reproduction Steps:
- Configure the website with a warehouse.
- Create/publish a delivery method with delivery type “Pick up in store”. Confirm the website has both
warehouse_id and in_store_dm_id
- Create a cart from the website shop using a storable product that has does not have "Sell When Out of Stock" turned on.
- Leave the cart without checking out.
-  On the generated quotation set the date to the past, but also the date must be after the website.send_abandoned_cart_email_activation_time
- Run the abandoned cart reminder scheduled action for the eligible abandoned cart with a storable product.

Related Ticket:
opw-6133986

Related PR:
https://github.com/odoo/odoo/pull/242864

When using test tags for js tests, some tests are not parsed correctly when containing brackets `[ ]`

This is because the tag selector use them to set parameters bounds as in `.test_method[test_param]`

The previous implementation using a regex could generate invalid test tags when the params contains comma, and brackets

This commits fixes this two ways:

Nested brackets will work, meaning that something like `.test_method[test, witch brackets[]]` will be correctly parsed as a tag `.test_method` with a parameter `test, witch brackets[]`since the brakets are balanced. Before, it was parsed as twho tags, `.test_method[test` and ` witch brackets[]]` the second one being considered invalid and spamming logs with errors

Brackets and backslashes can be escaped with a backslash, meaning that something like `.test_method[test, with brackets], and backslash\]` can be escaped as `.test_method[test, with brackets\], and backslash\\]`

Note that the parser will make it's best effort to parse non escaped strings, so a \ not followed by and escaped character will remain there in order to make potential copy paste easier. For the previous example
`.test_method[test, with brackets\], and backslash\` will work the same way.

So in practice, we only really need to escape \ when followed by another backslash or a bracket, and we need to escape brackets when they are not balanced.

Comma in hoot tests are also a problem since they are used to separate parameters, this can easily be tested by only splitting on `,@` since all hoot test should start with a @ and parameters of test_unit_* tests should be a list of hoot tests.

A followup pr will introduce the params to the canonical tag, and escape it as needed

Forward-Port-Of: odoo/odoo#261896
Forward-Port-Of: odoo/odoo#261516

**Steps to reproduce:**
* Install the **l10n_cz** module.
* Create a customer invoice for a Czech company.
* Print the invoice.

**Observed behavior:**
* The **Tax ID (DIČ)** is displayed **twice** in the invoice header in default layout.
* **VAT** is displayed **twice** in the invoice headed in folder layout.

**Cause:**
* The `registry_vat_external_layout` template adds `company.vat` to `company_address_list`.
* Base external layouts already include `company.vat` in the same list.
* This results in duplicated DIČ rendering.

**Fix:**
* Remove the redundant VAT `<li>` from `registry_vat_external_layout`.
* Keep only the Czech-specific **Company ID** (`company_registry`) entry, which is not provided by base layouts.

Before:
<img width="900" height="261" alt="image" src="https://github.com/user-attachments/assets/9b5b81aa-a79d-4c93-8109-3c97d79356f4" />

After:
<img width="804" height="221" alt="image" src="https://github.com/user-attachments/assets/4b62eddc-6117-4f52-a8fb-2b03812aad8b" />

opw-6125766

Forward-Port-Of: odoo/odoo#262399
Forward-Port-Of: odoo/odoo#260966