Currently, an error occurs when exporting an accounting report to 
PDF if any of the selected contacts do not have a name.

**Steps to reproduce:**
- Install the `account_reports` and `contacts` modules.
- Go to Contacts and open any contact (e.g., Azure Interior).
- Click `Add` > `Save & Close`, then `save` the contact.
- Navigate to Accounting > Reporting > Aged Receivable.
- Click `Partners` button and select the newly created contact (e.g., `Azure Interior, Other Address`).
- Click `PDF` to export the report.

**Error:**
`TypeError: sequence item 0: expected str instance, bool found`

**Root Cause:**
At [1], `options['selected_partner_ids']` is built using `partner.name`, which may 
be `False` for unnamed contacts. At [2], the `partner_value` list may therefore 
contain `False` entries coming from `options['selected_partner_ids']`. When 
calling `', '.join(partner_value)`, an error is raised because the list contains 
`non-string` (`bool`) values.

**Fix:**
This commit prevents errors when exporting reports to PDF and ensures 
that partner names are displayed in the report the same way as in the 
partner selection widget.

[1]:
https://github.com/odoo/enterprise/blob/a0ec2fcdc043cf52f1a646e84b9b97466072d47f/account_reports/models/account_report.py#L745

[2]:
https://github.com/odoo/enterprise/blob/099c7b94ad08f83873c05ec528e16fbf806f47f2/account_reports/data/pdf_export_templates.xml#L84-L93

opw-5467321

Forward-Port-Of: odoo/enterprise#105025
Forward-Port-Of: odoo/enterprise#103828

### Issue:
When having a template with a company but no department, it's not selected by new appraisal.

### Steps to reproduce:
- Have an employee whose appraisal date is today.
- Have only one template, with the company of the employee but no department
- Run the cron "Appraisal: Run employee appraisal"
- Open the Appraisals app
- Click on the newly created appraisal
- It doesn't have the template

### Cause:
- In `_compute_appraisal_template()`, only the department of the appraisal is used to compute the template.
But `_create_new_appraisal()` doesn't include the department in `appraisal_values` to create the appraisal.
So `appraisal.department_id` is `False` and the template from the department is ignored. 

- Another issue is if the employee has no department, then the appraisal also has no department.
Then no template is selected by the search domain. 

### Solution:
- Include `department_id` in `appraisal_values`
- Modify the search domain to include the case where the appraisal has no department

opw-5477450

_
## Short functional explanation of the error
When generating a payslip from a payrun for an employee on the swiss localization, the name of the PDF payslip is simply "new payslip" instead of "Salary Slip - <name of employee> - <time period of the slip>"

## Reproduction Steps
1. Install the app l10n_ch_hr_payroll.
2. Make sure you use a Swiss company.
3. Go to Payroll and click on the Payslips tab > payslips.
4. Click on Pay Run. Select Switzerland: ELM salaries and click Continue.
5. Select an employee for which you'd like to generate the payslip.
6. Click on the employee row in the list view.
7. Click Compute sheet > Print.

## Expected behavior
A PDF with name "Salary Slip - <employee name> - <time period>" is generated.

## Unexpected Behavior
A PDF with name "new Payslip" is generated.

## Origin of the issue
When printing the slip with this flow, we don't call the method
```_compute_name()``` used to compute the name of the current slip.
Therefore, it stays at 'New Slip', which is the default name.
Henceforth, we have to call this method manually when printing the
slip.
_
opw-5253811

**Steps to reproduce:**
- Install Accounting
- Go to Accounting dashboard

1) - On "Bank" journal card, select "Import File" option in dropdown menu
    - Upload a file containing a lot of statements (e.g. more than 170)
    - Test the import with "Test" button
2) - Open "Bank" journal
    - Select "Import records" in the cog menu
    - Upload a file containing a lot of statements (e.g. more than 170)
    - Test the import with "Test" button
3) - Open "Bank" journal
    - Click on "Upload" button
    - Upload a file containing a lot of statements (e.g. more than 170)
    - Test the import with "Test" button

**Issue:**
The issue happens when the test import fails.
Even if it was a test, all the records are created in the database.

**Cause:**
During a test import the records should not be reconciled after creation.
However, by default, "auto_statement_processing" property is True and trigger the reconciliation.
When an error is raised during the test import, a rollback is made on a previous savepoint.
But a commit can be done in "_cron_try_auto_reconcile_statement_lines" method, which results in the records being created for real.

**Solution:**
Set "auto_statement_processing" property to False for Test import.
For use case 1) and 2), we make sure that we follow the same flow than use case 3).

opw-5436937