Since migration of https://github.com/odoo/enterprise/pull/80399, some companies cannot retrieve easily their hr documents because their documents hr settings are not activated or not properly configured. With the new implementation, employee form view smart button redirect to the hr employee folder of the target employee. But if this folder does not exists after the migration or if the documents we not correctly placed in the HR folder before the migration, HR officers cannot retrieve the employees documents.

This fix makes the smart button redirect to employee folder if the settings are corrects and activated, but uses the old way to retrieve documents across the whole app if the setting is not active. I both cases, the smart button works as it should.

Also, we force having no owner on employee folders to avoid access gain by the applicant themselves when they sign their contract, creating a new employee with the applicant user in the context (making them, by default, owner of the created folder).

Task-4869292

Description of the issue/feature this PR addresses: 
Nilvera requires official codes on company contacts for submission to be compliant.

Current behavior before PR:
Invoices may be sent to Nilvera without the required codes, resulting in non-compliance. Currently, only the VKN and TCKN codes are sent, while other required codes are not supported.

Desired behavior after PR is merged: 
Official codes are added as non-deletable tags (non-mandatory ones archived). An error is raised when required tags are missing or empty. Invoices cannot be sent to Nilvera without valid codes. Codes are always reflected in both PDF and XML.

[IMP] l10n_tr_nilvera: support for official information codes

Added codes as tags from the official list and archived non-mandatory ones. These tags cannot be deleted, and an error is shown on attempt. Invoices are blocked from being sent to Nilvera if either MERSISNO or TICARETSICILNO is missing, or if assigned but without a value. Codes are reflected in both PDF and XML. 

task-4992049 

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

Forward-Port-Of: odoo/odoo#223931
Forward-Port-Of: odoo/odoo#223182

**Problem:**
When we have a combo product that has a variant product, if we order it from the Kiosk, all the variants for that product will be displayed. The extra price will also be added, even though it is not specified on the combo definition.

**Steps to reproduce:**
- Create a combo that has a variant product (like aluminium chair) 
- Go to the Kiosk and order said combo
- In the combo page, click on the variant, all the possible variants are displayed

**Why the fix:**
When creating a combo, we should specify which product variant we want, so that only those are displayed on the combo selection page. The way it is done right now, every variant is displayed whether we want them or not, without a way to refrain them from being displayed. After this commit, if the variants are specified on the combo, only
those are displayed in the Kiosk once we click on the combo. If we specify a product that has variants in the combo, all variants will still be displayed when clicking the product in the Kiosk, as it was before.

opw-4924019

Description
-----------
On a database where the user doesn't Secure their accounting entries regularly, it's possible over a long period to accumulate a lot of pending invoices that needs to be hashed.

This can lead to the processing of a large number of moves when opening the Secure Entries wizard, more specifically: 
```
-> `_compute_warnings`
    -> `_compute_hash_date`
        -> `_compute_max_hash_date`
            -> `_get_chains_to_hash`
```
While manipulating this large recordset, the ORM prefetcher will read *all* fields on the model upon the first cache miss, which usually are a lot, and some of them are quite large (label type fields).

This commit refactors the code to avoid any cache miss by fetching only what is necessary. This is achieved by:
- Use of a `_read_group` instead of 2 subsequent `groupby`
- Delegate `max` and `min` lookup to the database
- Explicitly fetch the fields that are going to be read
- Avoid the linear search into the associated statement lines for unreconciled moves
- Introduce a context key `chain_info_warnings` to skip the warnings computation of `_get_chain_info`, as it's unused for the context of `_compute_max_hash_date`.

Benchmark
---------
On a database with over 1.3M `account.move` that are pending hashing, opening the wizard for the Secure Entries took:

|              | Before* | After   | Improvement |
|--------------|---------|---------|-------------|
| Memory       | 6.8 GiB | 700 MiB | 9.9x        |
| Query Count  | 26.7k   | 18.5k   | 1.4x        |
| Timing SQL   | 41.2s   | 18s     | 2.3x        |
| Timing PY    | 7.29min | 14s     | 31.2x       |
| Timing Total | 7.98min | 32s     | 15x         |

\* - benchmark was taken with unlimited memory, the request takes more than 2 GiB -> OOM killed and never completes

Reference
---------
opw-5014345

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

Forward-Port-Of: odoo/odoo#225247
Forward-Port-Of: odoo/odoo#224105

#### Issue:
No taxes appear in the replace field when creating a new tax in a company based in Switzerland.

#### Step to reproduce:
- In a company based in Switzerland (l10n_ch)
- Create a new tax
- Add a Fiscal position other than "Switzerland national (+ Liechtenstein)"
- Click on the "Replace" field

#### Current behavior:
- No records are found

#### Expected behavior:
- Taxes from the "Switzerland national (+Liechtenstein)" fiscal position should appear

#### Cause of the issue
The Replace field display domestic taxes. Domestic taxes are part of the same fiscal position which is computed as domestic. In the l10n_ch module no fiscal position is computed as `domestic_fiscal_position_id`. Indeed in `account.fiscal.position-ch.csv` the fiscal position we want to be domestic is linked to a `country_group_id`, but no `country_id`. However the domestic fiscal position is computed from `country_id` only. Therefore Switzerland has no `domestic_fiscal_position_id`.

#### Solution:
This issue already happened [once](https://github.com/odoo/odoo/pull/208810) for an other localization. To avoid the situation to happen again in the future this commit adapts the `_compute_domestic_fiscal_position_id` to include fiscal position with no `country_id` but a `country_group_id`.


opw-5011527

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

_______________________________________
## Short functional explanation of the error
Let's say that you have a contact of type Company and a child contact of type Individual. Both share the same company_id. But when exporting the individual, deleting its company in the downloaded .xlsx file and importing it again, it overrides the already existing individual, resulting in a single individual contact without company_id nor parent company. However, the contact of type company will still have the individual as its child, creating an inconsistency. This leads to errors in other modules as the rules aren't respected by these records anymore.

## Reproduction Steps
1. Go to the contact application and create a contact of type Company. Set an email and click on the Sales and Purchase tab and set a Company.
2. Go back to the Contacts tab and click on add contact. Click the radio button Contact, set an email and hit Save and Close.
3. Go back to the Contacts app. You should see 2 more contacts: one corresponding to the company and one corresponding to the individual.
4. Select the Individual contact and click Actions > export. Check 'I want to update data (import-compatible export)' and on the left panel, click on the + button next to Company. Then, click export.
5. Click on the file it generates and remove the company, then save.
6. Click on the cog next to Contacts on the top left and click Import Records. Then, click on Upload Data file and select the file you just exported. You should see that the field company_id has no value. Click Test then Import.

### Expected behavior
Either an error message should show up or the link between the Company contact and its child should be removed.

### Unexpected behavior
The individual contact containing the link to its parent Company contact is overridden by the contact we just imported, which doesn't have a link to the parent company contact. However, the company contact conserves a link to the child individual contact. This means that one way of the 2-ways link has been deleted, creating an inconsistency.

## Origin of the issue
We can override res.partners using the names and email addresses, which are primary keys, but the code doesn't check the consistency of parent/ children links.

_________________________________________
opw-4976400





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

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#92908
Forward-Port-Of: odoo/enterprise#91565

**Step to reproduce:**
    - install "project_account_budget"
    - go to accounting > accounting > Analytic Budget
    - create a budget of type expense,say test budget
    - select analytic account `Asustek - Wood Corner`
    - set budget amount => 500. open the budget
    - create a new project 'test project"> open setting > Analytic Page
    - add `Asustek - Wood Corner` analytic account in project field
    - create a PO with amount > 500
    - in analytic distribution column, add `Asustek - Wood Corner` in project column
    - confirm PO and create Bill
    - Go to `test project` settings > Dashboard smart button
    
**Observation:**
    - For exceeding expense budget, we have green color in budget section
    - It should be red
    
**Cause:**
The conditional class for budget progress was incorrectly evaluated due to missing parentheses around the `and` condition.

In expressions like:
`(true and (1 == 1 ? 'a' : 'c')) or (1 == 1 ? 'b' : 'd') → 'a'` ✅
 `true and 1 == 1 ? 'a' : 'c' or 1 == 1 ? 'b' : 'd'       → 'b'` ❌

Without parenthesis, the `or` clause is evaluated unexpectedly, even when the `and` branch is intended to take precedence.

This commit wraps the `and` condition in parentheses to ensure the correct evaluation order and consistent class assignment.

Budget:
<img width="1203" height="291" alt="budget 4968162" src="https://github.com/user-attachments/assets/2d8223d5-0344-4ad0-b33c-2598ea167f2d" />

 
Before fix:
<img width="623" height="195" alt="before fix 4968162" src="https://github.com/user-attachments/assets/4ac749bf-fa93-4835-963a-5dfbdd05559d" />

After fix:
<img width="643" height="225" alt="after fix 4968162 " src="https://github.com/user-attachments/assets/4fd228f9-e32f-48d9-b6ef-55251b21d601" />


opw-4968162

Forward-Port-Of: odoo/enterprise#91617

Currently, when having a CL Company an dusing the POS, it is possible to have the POS crash when validating orders.

Steps to reproduce:
-------------------
* Install l10n_cl_edi_pos
* Create a new company
* Put Chile as country
* Switch to that company
* Create a shop and open it
* Make a sale, validate order
> Observation: POS Crashes

Why the fix:
------------
The crash is happening upon trying to render the receipt because `l10n_cl_dte_resolution_date` is undefined.

`l10n_cl_dte_resolution_date`is a field that can be found on the company settings only if the field `l10n_cl_dte_service_provider` is set and is required when the later has either `SII` or `SIITEST` as value.

For companies in Chile, there is therefore two setups that leads to having `l10n_cl_dte_resolution_date` undefined. Either the service provider is set to demo, which case clients don't need to fill in the resolution date, either the provider is left empty (since not required upon company creation).

Since the field can be undefined, we don't render it when it is.

opw-5034091

*= documents_fleet

Currently, when user tries to link a document with a vehicle and if there is no vehicle exists an error is raised.

**Steps to Reproduce:**
1) Install `documents_fleet` module(without Demo Data).
2) Open Documents App.
3) Upload a file in `Fleet` folder.
4) Select the uploaded file and click on `'Link to a vehicle'` button.

Error:
`ValueError: invalid literal for int() with base 10: 'False'`

Root Cause:
The `link_to_record` method attempts to find the first record of the target model to use as a default value when opening the linking wizard. If no records exist, the search returns an empty recordset, and accessing `.id` at [1], on it results in the value `False`. The code then incorrectly constructs a default reference string like `fleet.vehicle,False`. The wizard crashes when it tries to parse this string and convert the `False` part to an integer.

Solution:
This commit prevents error by ensuring that the user cannot link a document to a model without existing records.

[1]- https://github.com/odoo/enterprise/blob/83640d21b2c31ed9d572c48e02a9aeea9eb1607b/documents/models/documents_workflow_rule.py#L113

sentry-6792079496

Forward-Port-Of: odoo/enterprise#93738
Forward-Port-Of: odoo/enterprise#91888