Currently, an error occurs when a user tries to add a sub-task and try to sort subtasks w.r.t `My Deadline` column (which is not stored) before saving.

**Steps to produce:**

- Install the `project` module.
- Navigate to `Project > Tasks > All Tasks` and open any task.
- In the Sub-tasks page, unhide the `My Deadline` field.
- `Add a line` and sort subtasks w.r.t `My Deadline`, then try to `save`.

**Error:**
`ValueError: Cannot convert project.task.my_activity_date_deadline to SQL` `because it is not stored`

**Root Cause:**
The `my_activity_date_deadline` field on the Task model is computed and not stored in the database. When a user sorts a sub-task list by this column and then saves the parent task,at [1] the odoo tries to reload the list with a SQL `ORDER BY` clause on this non-existent column. The ORM cannot translate a non-stored field into SQL for ordering, which causes the ValueError.

[1]- https://github.com/odoo/odoo/blob/39b232d640d9e1e09d10e4984ebe419dbe885393/odoo/orm/models.py#L5625-L5626

Used Reference:
In CRM Lead `my_activity_date_deadline` is also used for sorting in the list view, but handled it's sorting manually by overriding `search_fetch` method as shown below:

https://github.com/odoo/odoo/blob/39b232d640d9e1e09d10e4984ebe419dbe885393/addons/crm/models/crm_lead.py#L782-L788

**Solution:**
This commit makes the `my_activity_date_deadline field` sortable by overriding the `search_fetch` method on the project.task model.

sentry - 6604203533

Currently, an error occurs when the user attempts load scenario data through a server action.

Steps to replicate:
- Go to `Server Actions > search `Load Demo Data` > Create contextual action`.
- Go to Recruitment > go to Job Positions form view > Run the server action twice, and you will get the error.

Error:
`ValueError: ParseError('while parsing /home/odoo/odoo18/community/addons/...')` `UniqueViolation: duplicate key value violates unique constraint 'documents_document_attachment_unique'`

This error occurs due to a unique  constraint on documents, which causes a uniqueness violation on ir.attachment [1] when attempting to import the same record twice.

This commit fixes the issue by checking if the scenario data has already been imported. If it has, the import is skipped to prevent uniqueness violation.

[1]-https://github.com/odoo/odoo/blob/4b4fb5b9a655db4d3b9adb8d6a875f01d27a4806/addons/hr_recruitment/data/scenarios/hr_recruitment_scenario.xml#L194

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

**Steps to reproduce:**
1. Install Sales.
2. Create an email template for the 'sale.order' model and assign it to the admin user under the settings page in the 'User' field.
3. Log in as the demo user.
4. Create a quotation and click the 'Send by Email' button.
5. In the wizard, click the three dots between the attachment and AI logo in the footer.
6. Observe the templates list.

**Issue:**
  - The template created for the admin user appears for the demo user as well.

**Cause:**
https://github.com/odoo/odoo/blob/07626050bd0104fecd8799b56d30245d00da3f27/addons/mail/static/src/core/web/mail_composer_template_selector.js#L31-L44
 - The domain used to fetch templates was incorrectly filtering for templates
  assigned to any user (instead of filtering for templates assigned to
  the current user or not assigned at all).

**Solution:**
 - Corrected the domain to include only templates assigned to
  the current user and not assigned to anyone.

opw-4901492

Forward-Port-Of: odoo/odoo#217641

#### Issue:
Only the vendor name of a product is displayed on a purchase order on all pages except the first one.

#### Step to reproduce:
- make sure "Variant grid entries" is disabled in the settings. If you can't disable it, you can disable the view `purchase.order.form.inherit.matrix` to trigger the bug.
- Create a product
- Go to the purchase sheet
- Add a vendor
- Add the field "Vendor Product Name" and "Vendor Product Code" and fill them
- Create a purchase order
- Add your product
- Add your product a second time (on a second line)
- Confirm the PO
- Activate debug mode
- Go to the view and add a limit to have only 1 POL per page
- Return to your PO
- Go to the second page

#### Current behavior:
- Only the vendor name is displayed

#### Expected behavior:
- The vendor name should appear at the top, while the db name should be displayed under as in the first page.

#### Cause of the issue:
On the first page, POLs data are fetch through a `web_read` on the PO, while on other pages data are fetch through `web_read` on the POLs of the page. 
While fetching POL data with a `web_read` the client ask for several informations including: `name` and `product_id.display_name`. If both return the same, the client show only one, else it shows the `display_name` on top and the `name` below.
- `name` return the vendor name 
- `product_id` is fetch with the context `partner_id` which transform the `display_name` from the db_name to the Vendor name
Therefore it fetches twice the vendor name and don't have the name from the db.

#### Solution:
- remove the `partner_id` from the context.

#### Consequence:
- When adding a product to the PO, the name of the product displayed in the dropdown list will be the name from the db instead of the name of the vendor.

PO confirmed that consequence is OK as long as it's still possible to search for product using vendor code, which is still possible.

opw-4737337

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

Forward-Port-Of: odoo/odoo#223250

If the document is empty we don't need to check for encryption. Otherwise we risk getting an error.

```
Traceback (most recent call last):
  File "/home/odoo/src/odoo/18.0/odoo/tools/convert.py", line 544, in _tag_root
    f(rec)
  File "/home/odoo/src/odoo/18.0/odoo/tools/convert.py", line 444, in _tag_record
    record = model._load_records([data], self.mode == 'update')
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/odoo/src/odoo/18.0/odoo/models.py", line 5500, in _load_records
    data['record']._load_records_write(data['values'])
  File "/home/odoo/src/odoo/18.0/odoo/models.py", line 5418, in _load_records_write
    self.write(values)
  File "/home/odoo/src/odoo/18.0/odoo/models.py", line 4827, in write
    real_recs._validate_fields(vals, inverse_fields)
  File "/home/odoo/src/odoo/18.0/odoo/models.py", line 1631, in _validate_fields
    check(self)
  File "/home/odoo/src/odoo/18.0/addons/sale_pdf_quote_builder/models/product_document.py", line 46, in _check_attached_on_and_datas_compatibility
    utils._ensure_document_not_encrypted(base64.b64decode(doc.datas))
  File "/home/odoo/src/odoo/18.0/addons/sale_pdf_quote_builder/utils.py", line 12, in _ensure_document_not_encrypted
    if pdf.PdfFileReader(io.BytesIO(document), strict=False).isEncrypted:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/odoo/src/odoo/18.0/odoo/tools/pdf/__init__.py", line 91, in __init__
    super().__init__(stream, strict)
  File "/home/odoo/.local/lib/python3.12/site-packages/PyPDF2/_reader.py", line 317, in __init__
    self.read(stream)
  File "/home/odoo/.local/lib/python3.12/site-packages/PyPDF2/_reader.py", line 1408, in read
    self._basic_validation(stream)
  File "/home/odoo/.local/lib/python3.12/site-packages/PyPDF2/_reader.py", line 1449, in _basic_validation
    raise EmptyFileError("Cannot read an empty file")
PyPDF2.errors.EmptyFileError: Cannot read an empty file
```

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Forward-Port-Of: odoo/odoo#224674

Currently, an error occurs when attempting to find duplicate transactions in the bank.

Steps to Reproduce:
- Install the `Accountant` module.
- In the `Accounting` Dashboard, click on `Bank`.
- In Actions, click `Find Duplicate Transactions`.
- Clear the `Starting Date` and click save.

Traceback:
```py
psycopg2.errors.UndefinedFunction: operator does not exist: date >= boolean
LINE 6:                    AND move.date >= false
                                         ^
HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.
```

This error occurs when the system attempts to detect duplicate transactions without a `Starting Date`. During the check, it evaluates the condition `move.date >= date_from`. Since `date_from` is False, the comparison triggers an error.

This commit ensures that if the `Starting Date` is empty when finding duplicate transactions, it uses today’s date as the `Starting Date`.

Reference commit: https://github.com/odoo/enterprise/pull/87000/commits/806ab2d56952e9d0f597cf1ab36ea2f180a84323

Fix `sign_tour`. 

How to reproduce: 
1. Go to tours in Odoo
2. Look up sign_tour
3. Click testing ( If testing stops at Sign App, change search filters or archive sign all .request records so that the following screen displays )
<img width="780" height="591" alt="image" src="https://github.com/user-attachments/assets/b164c224-0e3e-4dce-97e6-89848263e59e" />

4. tour fails! 

---
First commit 

The `sign_tour` was failing after the conversion of the `sign.Template` client action to OWL. The standard `drag_and_drop` tour helper can no longer be used for automatic tour testing because the drop target is inside an iframe whose content is managed by PDF.js.

This commit fixes the tour by utilizing the custom helper function, `dragAndDropSignItemAtHeight`, to programmatically simulate the drag and drop action.

---

Second commit

The step "footer.modal-footer button.btn-primary:enabled" assumes that the Signature Dialog opened from its previous step ("Sign It" navigation button).

However, the "Sign It" navigation button does not always open the dialog.

If signing user (res.users) already has "sign_signature" data, the data will be automatically filled in to the Signature input.

Otherwise, the navigation button will open the Signature Dialog.

Luckily, we can see whether user has "sign_signature" data or not by checking if the <input data-item_type='signature'/> node has "data-auto_value" attribute or not.

We now skip the step if data-auto_value is set for signature.

---

Third commit

If `sign.template_sign_tour` has sign request, it means that the template might have a sign item because the `sign_tour` tour adds the Signature sign item to the template. (If user followed the tour)

When we're copying the sign template to trigger the template tour, we should not copy the sign item. User will be guided to add the sign item during the tour.


---

Note:
ci/security needs to be overriden as it was done for https://github.com/odoo/odoo/pull/134793#issuecomment-1711440188
---


opw-4752794

Forward-Port-Of: odoo/enterprise#91565