Steps to Reproduce:
------------------
- Open Helpdesk.
- Go to Configuration → Helpdesk Teams.
- Create a new team.
- Enable the Billing feature and assign a project to this team.
- Set the project’s Company field to Null.
- Create an employee for the current user in another company.
- Ensure the user has employees in both companies.
- Create a new ticket (or open an existing one) in the newly created team.
- Try creating a new timesheet → a Validation Error is raised.

Root Cause:
-----------------
When a user has employees associated with multiple companies and tries to log a timesheet with multi-company enabled, a validation error occurs.

**This happens because:**

- The default company is derived from the project linked to the Helpdesk team. Since the company_id field on the project is no longer required, it may be Null, leading to an error when fetching the correct [employee for the company](https://github.com/odoo/odoo/blob/6a36015e2ee69aafe3880bf1fff38439af5cd673/addons/hr_timesheet/models/hr_timesheet.py#L214-L216
).

- Additionally, the [company check](https://github.com/odoo/enterprise/blob/83a1b88c8cae4db5c9b1bf82ee7ebb4e13c41b2a/helpdesk_timesheet/models/analytic.py#L81-L82) is incorrect. The code is checking whether the `company_id` key exists in a `list of vals`, whereas it should be checked directly on the vals dict itself. 

Issue Faced:
-------------
In version 18.3, timesheets are created during migration [here](https://github.com/odoo/upgrade/blob/24f85bbc3408bf10b1cee93e4c395edf806beaa8/migrations/helpdesk_timesheet/saas~18.3.1.0/post-migrate.py#L44-L58 ). Even though the correct company_id is passed, it gets overridden during the process. and If the associated project does not have a company set, the company_id becomes False [here](https://github.com/odoo/enterprise/blob/83a1b88c8cae4db5c9b1bf82ee7ebb4e13c41b2a/helpdesk_timesheet/models/analytic.py#L81-L82),
 which results in a Validation Error because the [here](https://github.com/odoo/odoo/blob/6a36015e2ee69aafe3880bf1fff38439af5cd673/addons/hr_timesheet/models/hr_timesheet.py#L214-L216) unable to determine the correct employee linked to the company. 

OPW: 5004092

Forward-Port-Of: odoo/enterprise#95226
Forward-Port-Of: odoo/enterprise#92507

Currently, an error occurs when a new user tries to load demo data in the `Appraisal` module.

Steps to reproduce:
---
- Install `hr_appraisal` module (without demo data)
- Create NEW user > Login with new user
- Open `Appraisal` and Click `Load Demo Data`

Traceback:
---
```py
ParseError: <record id="calendar_event_appraisal_1" model="calendar.event" forcecreate="1">
            <field name="user_id" ref="base.user_admin"/>
            <field name="name">Appraisal of Emma Granger</field>
            <field name="partner_ids" eval="[(6,0,[ref('hr.work_contact_sj'), ref('hr.work_contact_mw'),                 ref('hr.work_contact_eg')])]"/>
            <field name="start" eval="(DateTime.now() + relativedelta(months=1)).strftime('%Y-%m-%d 07:00:00')"/>
            <field name="stop" eval="(DateTime.now() + relativedelta(months=1)).strftime('%Y-%m-%d 09:00:00')"/>
            <field name="res_model_id" ref="hr_appraisal.model_hr_appraisal"/>
            <field name="res_model">hr.appraisal</field>
            <field name="res_id" ref="hr_appraisal.hr_appraisal_1"/>
        </record>

ValueError: ParseError('while parsing /home/odoo/odoo/enterprise/hr_appraisal/data/scenarios/hr_appraisal_scenario.xml:561, somewhere inside\n<record id="calendar_event_appraisal_1" model="calendar.event" forcecreate="1">\n            <field name="user_id" ref="base.user_admin"/>\n            <field name="name">Appraisal of Emma Granger</field>\n            <field name="partner_ids" eval="[(6,0,[ref(\'hr.work_contact_sj\'), ref(\'hr.work_contact_mw\'),                 ref(\'hr.work_contact_eg\')])]"/>\n            <field name="start" eval="(DateTime.now() + relativedelta(months=1)).strftime(\'%Y-%m-%d 07:00:00\')"/>\n            <field name="stop" eval="(DateTime.now() + relativedelta(months=1)).strftime(\'%Y-%m-%d 09:00:00\')"/>\n            <field name="res_model_id" ref="hr_appraisal.model_hr_appraisal"/>\n            <field name="res_model">hr.appraisal</field>\n            <field name="res_id" ref="hr_appraisal.hr_appraisal_1"/>\n        </record>') while evaluating
'action = model._load_demo_data()'
```

This error occurs because the new user has not been granted administrative rights.

This commit resolves the issue by granting the user superuser rights.

sentry-6110523247

Forward-Port-Of: odoo/enterprise#93461

This PR contains two commits, the first is a refactoring, and the second is the invoice printing itself.

- **[REF] iot: extract printer select into separate function**
  Before this commit, the printer selection wizard was tightly coupled to
  the IoT report handler, and the call to send to the printer was
  duplicated in the wizard and the handler.
  
  After this commit, the printer selection wizard is contained in a
  function that will always return the selected printers directly to the
  caller, whether the dialog needs to be opened or not. The wizard is
  simplified as a result and the print call always occurs in the handler.
  
  This refactoring will allow other places to use the printer selection
  wizard, namely for invoice printing.


- **[FIX] pos_iot: print invoices via IoT**
    In the commit https://github.com/odoo/enterprise/commit/07418d7544ceecfef38257db8f59bf845a0b0769, the invoice PDF downloading was refactored to
  bypass the `ir.actions.report` model, instead working directly via an
  action on the invoice model. A side effect of this is that it broke
  printing invoices via the IoT, as it relies on the report printing
  action to function.
  
  To fix this, this commit introduces an override in `pos_iot` for the
  `account_move_service`, which will print the invoice PDF via the IoT
  instead of downloading it directly (if a printer is associated with the
  report).
  
  
task-5109814

Forward-Port-Of: odoo/enterprise#95586