This fix corrects an issue where depreciation entries for assets created in a subsidiary company were incorrectly assigned to the parent company instead of the subsidiary. When users create an asset in a subsidiary company and view the posted depreciation entries, they will now correctly see entries assigned to the subsidiary company rather than the parent company.

When creating an asset from sub company when both
sub company and parent company are selected,
the asset's depreciation moves have the parent company
instead of the child one.

Steps:

- Have a parent company P and a child company C
- With companies set to P + C, and company set to C
- Create an asset and compute board
- Click on "Posted Entries" smart button
-> Entries have P as company instead of C

opw-4059496

This fix ensures that when starting a work order in manufacturing, the system properly validates whether the employee attempting to start the work is authorized to work on that specific work center. Previously, unauthorized employees could start work orders without triggering an error, which could lead to compliance and operational issues. Now the system correctly prevents unauthorized employees from starting work orders.

Steps to reproduce the bug:
- Log in as Mitchell Admin.
- Go to Work Centers > Assembly Line 1 > Select Mark Demo in the allowed employees.
- Create a storable product P1 with BoM:
    - Components: Select any product.
    - Operation: OP1 in Assembly Line 1.
- Create a manufacturing order to produce one unit of P1.
- Try to start the work order with Mitchell from the form view.

Problem:
No user error is triggered when it should be.

opw-4045726

This fix ensures users must select at least one printer before printing reports through the IoT system. Previously, users could click Print without selecting a device, which would result in nothing being printed and the system remembering this preference, preventing future print attempts. Now, if no printer is selected, the system displays a notification and prevents the print action.

Currently, when printing reports using the iot, if we don't select a device when the wizard prompts ut to do so, nothing will be printed and it will be saved in the browser storage that no printer should print this report.

Steps to reproduce:
-------------------
* Connect the IOT to the db
* In developper mode go to: **Settings** > **Technical** > **Actions** > **Reports**
* Select `PDF Quote` for example and associate a printer
* Go to the **Sale** App and select any quotation
* Select the gear icon
* Select **Print** > `PDF Quote`
* Select `Print` without selecting a printer
> Observation: Nothing is printed
* Select **Print** > `PDF Quote`
> Observation: Nothing is printed and the prompt does not appear

Why the fix:
------------
The idea behind this fix is to make it mandatory to choose at least one of the devices on the wizard prompt.

If at least one printer is selected we continue with the printing. If not, we put a notification on screen and don't do anything else.

opw-4019575

Current behavior with the fix:
--------------------------------------
![no_printer_selected](https://github.com/user-attachments/assets/2a98404a-274e-4aae-868c-c74a870ad75c)

This fix corrects an issue where archived price lists were being included in rental product pricing calculations, which could result in incorrect prices being displayed or used. By excluding archived price lists, the system now shows only active pricing information and ensures accurate rental price quotes.

The product_pricing_ids didn't exclude archived pricelist which could lead to wrong price. While also displaying unnecessary data.

opw-4053690

This update fixes a bug where old articles marked for deletion were not being automatically removed from the system. The issue was caused by a missing setting that prevented the system from finding archived articles. With this fix, the automatic cleanup process now works correctly and removes old, unused articles as intended.

This commit fixes an issue with the garbage collecting of knowledge articles. Old articles weren't being unlinked after they due date was passed.

This is caused by a missing context key `active_test` which enables us to search articles that could be archived.
Since `to_delete` articles are considered as archived, the original search never found any article to remove.

Now, the context is added enabling the autovacuum to do its job and remove old useless articles.

task-4047720

Forward-Port-Of: odoo/enterprise#66586