This fixes a visibility issue in the Website editor where link editing popovers could become unreadable when a dark site background was selected. The popover now keeps neutral interface colors, making editing links reliable regardless of the website theme, and the frontend-to-backend button no longer inherits theme fonts.

Steps to reproduce the issue:

- Enter Website edit mode.
- Click on the "Theme" tab.
- Pick a black color for the website background (4th color button).
- Click on a link in the website navbar to make the link popover appear.
- Bug: The popover background is black, and its buttons are not visible as they are also black.

Bug introduced by this commit [1], where popover colors were updated to match the website's theme. The goal was to align popovers, such as the one for the e-commerce cart button, with the theme colors. However, the change unfortunately also affected the link editing popover, which should remain neutral as it is part of the interface elements.

[1]: https://github.com/odoo/odoo/commit/0d96be06faf8aad1a92183bd2b6371253980c7e6

task-4422810

| Before  | After |
| ------------- | ------------- |
| ![image](https://github.com/user-attachments/assets/a217c886-9521-4347-a0db-7d6cd7b6029b)  | ![image](https://github.com/user-attachments/assets/f06e4618-e896-430c-8063-bbe3dd534055)  |

Fixes the mobile layout for expense list and kanban screens so action buttons collapse into a dropdown instead of crowding the page. This makes expense management easier to use on smaller screens and prevents important controls from being awkward or hard to access.

The survey question layout has been adjusted so warning messages no longer cover the comment field for multiple-choice questions with multiple answers allowed. This makes the survey form easier to read and complete, reducing confusion for respondents.

One issue remained for the 'Multiple choice: multiple answers allowed' option in this task:
https://www.odoo.com/odoo/project.task/4663115

Task- 4663115

Printing draft invoices for Swiss customers no longer fails when QR code payment details are enabled. The system now skips QR code generation for draft invoices, allowing users to generate the PDF normally until the invoice has a final reference.

Steps to reproduce:
- enable qr code
- create an invoice with a swiss client
- try to print it

Issue:
An error is raised

Cause:
There is no reference for a Swiss invoice in draft. If there is no reference, it is not possible to print the qr code in Switzerland.

Solution:
We prevent QR code generation whenever the invoice is in draft.

opw-4585574

This fix improves the Dashboard view for users working in right-to-left languages such as Arabic or Hebrew. Text in the top dashboard canvas is now visible and presented correctly, making the dashboard easier to read and use.

[FIX] spreadsheet : Dashboard view for rtl languages

Steps to reproduce:
	1- Install any right-to-left language
	2- Open Dashboard application
	3- Check the view of the top canvas
	
Current behavior before PR:
The text in the top canvas in the dashboard app when using a right-to-left language is not shown in a good way

Desired behavior after PR is merged:
The view has been fixed and the text is visible now

opw-3592360

Undoing the Description option on website form fields now correctly restores the previous field state. This prevents fields from losing spacing, appearance, and editing options, helping website editors work without accidentally breaking form layouts.

In a form snippet, enabling the "Description" option for a field and then undoing this action caused the field to lose its styling and available customization options.

Steps to reproduce:
- Enter Edit mode.
- Add a Form snippet.
- Select any field (e.g., "Your Name").
- Enable the "Description" option from the customization panel.
- Undo the action (Ctrl+Z).

This results in the field losing its padding and the "Description" and other options being removed.

Cause:
A redundant line of code was adding an extra step in the mutation history. When undoing, this extra step caused the removal of essential classes from the field, leading to the loss of styling and options.

Fix:
Removed the redundant line to ensure undoing the action correctly restores the previous state without affecting the field’s styling or customization options.

task-4013551

This fix restores the product price area in the website shop editor after a previous change hid too much of it. Businesses can still hide zero-price sales when needed while keeping prices editable in the website editor.

In a previous commit 4a6af867dd2eb13659c93e553d5e553cacb3048d, price was intended to be hidden when prevent zero sale is enabled.

However the fix wrongly removed the outer div containing also the editable price that can be updated from the editor.

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

This fix addresses an intermittent issue in Web Studio's automated checks that could cause inconsistent test results. It helps keep validation more stable, reducing noise for teams monitoring product quality.

Description of the issue/feature this PR addresses: As per ZATCA, `For electronic invoices generated in PDF/A-3 format: while the PDF content will be the representation of the XML invoice in a human readable format, the XML invoice itself will still be added as an attachment as specified in ISO 19005-3 titled "Document management - Electronic document file format for long -term preservation - Part 3: Use of ISO 32000-1 with support for embedded files (PDF/A-3)", and contain the compliant

Description of the issue/feature this PR addresses:

As per ZATCA, 

`For electronic invoices generated in PDF/A-3 format: while the PDF content will be the representation of the XML invoice in a human readable format, the XML invoice itself will still be added as an attachment as specified in ISO 19005-3 titled "Document management - Electronic document file format for long -term preservation - Part 3: Use of ISO 32000-1 with support for embedded files (PDF/A-3)", and contain the compliant XML invoice as an embedded object.`

Current behavior before PR:
- Generated Saudi Localization PDF Invoice had not embedded attached EDI XML documents
- Generated Saudi Localization PDF Invoice was not PDF-A Compliant
- Generated Saudi Localization PDF Invoice file name did not adhere to ZATCA business rules of the following:
`Seller Vat Number (BT-31), Date (BT-2), Time (KSA-25), Invoice Number (BT-1)`

Desired behavior after PR is merged:
- Generated Saudi Localization PDF Invoice has the XML  EDI documents embedded as an attachment
- Generated Saudi Localization PDF Invoice is PDF-A Compliant
- Generated Saudi Localization PDF Invoice is named as per the ZATCA business rules

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

opw-4528551

Forward-Port-Of: odoo/odoo#198158