Problem:
Power buttons are shown regardless of the editor field's actual rendered width, causing them to overlap other menus when the field is small.

Solution:
Instead of relying solely on the global `ui.isSmall` (mobile detection), check the editor field's own width and hide power buttons whenever it falls below the overlap threshold.

Before:
<img width="576" height="301" alt="image" src="https://github.com/user-attachments/assets/dcebed55-5c80-4fe5-8d33-c320549cf347" />

After:
<img width="542" height="336" alt="image" src="https://github.com/user-attachments/assets/34a233bb-9958-43ac-adb9-04702a2e403d" />

Steps to reproduce:
- Change languange (French to have a long placeholder).
- Settings > Customer Invoices > Default Terms & Conditions.
- Check "Add a Note".
- Resize the screen to smaller size.
- Observe the power buttons overlap with the translate button.

task-6117734

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

Steps to reproduce:
**Note: This does not occur in Peppol demo mode**
1. Install the Peppol module and enable it in Settings
2. Create a portal user, then go to the 'Accounting' tab in their contact record
3. Under Customer Invoices, set the following:
a. Invoice Sending -> By Peppol
b. eInvoice Format -> Peppol Bis 3.0
c. Belgian VAT -> A valid VAT
4. Click 'Verify' under 'Peppol Status' and this should change `peppol_verification_status` to `valid`
5. Disable Peppol in Settings
6. Log in as the created user and make a purchase on the web shop
7. Observe that no sale order confirmation email is sent, and a singleton error is logged.

When Peppol is installed, but disabled, the `account_peppol_edi_user` field is not set (or gets unset) on the company, which can lead to a singleton error when trying to send an invoice via Peppol. This can occur if Peppol was previously enabled and there were `res.partner` records with Peppol information that was validated. The database checks this after E-Commerce transactions and, if there is no `invoice_sending_method` set on the `res.partner` record, it defaults to Peppol, even if it is disabled, which can cause the singleton error. This change will ensure that we check to see if the company has registered with Peppol before using it to send invoices.

[Ticket link](https://www.odoo.com/odoo/project.task/5890740)
opw-5890740

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