Currently a traceback occurrs from multiple places when there is no tz for employee and used in the `pytz.timezone` method.

https://github.com/odoo/enterprise/blob/517983ae9deec37795eb11522134a1f5ade31e9b/hr_payroll/wizard/hr_payroll_payslips_by_employees.py#L131

For instance, if there is no tz in resource_calendar_id, it leads to a traceback.

Error: 
```
AttributeError: 'bool' object has no attribute 'upper'
  File "odoo/http.py", line 2364, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1892, in _serve_db
    return self._transactioning(
  File "odoo/http.py", line 1955, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 137, in retrying
    result = func()
  File "odoo/http.py", line 1922, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2169, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 329, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 727, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/web/controllers/dataset.py", line 35, in call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "odoo/api.py", line 517, in call_kw
    result = getattr(recs, name)(*args, **kwargs)
  File "addons/web/models/models.py", line 70, in web_save
    self.write(vals)
  File "home/odoo/src/enterprise/18.0/hr_payroll/models/hr_contract.py", line 429, in write
    res = super().write(vals)
  File "addons/hr_work_entry_contract/models/hr_contract.py", line 453, in write
    contract._recompute_work_entries(date_from, date_to)
  File "home/odoo/src/enterprise/18.0/hr_payroll/models/hr_contract.py", line 441, in _recompute_work_entries
    self._recompute_payslips(date_from, date_to)
  File "home/odoo/src/enterprise/18.0/hr_payroll/models/hr_contract.py", line 453, in _recompute_payslips
    all_payslips.action_refresh_from_work_entries()
  File "home/odoo/src/enterprise/18.0/hr_payroll/models/hr_payslip.py", line 601, in action_refresh_from_work_entries
    payslips._compute_worked_days_line_ids()
  File "home/odoo/src/enterprise/18.0/hr_payroll/models/hr_payslip.py", line 1141, in _compute_worked_days_line_ids
    slip_tz = pytz.timezone(slip.contract_id.resource_calendar_id.tz)
  File "odoo/_monkeypatches/pytz.py", line 129, in timezone
    return original_pytz_timezone(name)
  File "__init__.py", line 183, in timezone
    if zone.upper() == 'UTC':
```

To resolve this issue we can give a default value of `UTC` is there is no name. which makes the code more robust.

sentry-6134147853, 6119911834

Currently, an error occurs when computing a display name for stock quant.

Step to produce:

- Install the `stock` module(without demo data).
- Go to inventory settings, enable Packages, Quality, Quality Worksheet, Reception Report, Variants, Units of Measure, Product Packagings, Lots & Serial Numbers, Display Lots & Serial Numbers on Delivery Slips, Expiration Dates, and Dropshipping.
- Disable the Barcode Scanner.
- After that, enable 'Display Lots & Serial Numbers on Invoices' in the Valuation section
- Create a product and enable the 'Track Inventory' option.
- In the product form view, click on On Hand in the breadcrumbs to navigate to the stock quantity list view
- Create a new record to update the quantity.
- Click on the 'View' button, remove the location, and try to come back to update quantity list view.

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

This error occurs because we compute the display name of stock quant and it is derived from location_id, lot_id, package_id, or owner_id. If none of these values are present in stock quant then the system tries to concate the False (bool) value with a string at [1] and an error occurs.

Link [1]: https://github.com/odoo/odoo/blob/be6b327c17435947fc3f10d30fc8c4730c182aed/addons/stock/models/stock_quant.py#L585-L592

To resolve this issue, Assign a default display name of stock quant if none of the values of fields (location_id, lot_id, package_id, owner_id) are available.

Sentry-6165002037


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

When user edits mail template html and pastes an image tag with invalid encoding it throws an error.

**Steps to reproduce:**
* Install Email marketing and activate developer mode.
* Email marketing>New>Mail Body> Start From Scratch>click `</>` icon
* Paste any improper image element which doesn't have proper base64 encoding, for example: 
`<img src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU 5ErkJgg'/>`
* Enter any Subject name and save.

`binascii.Error: Invalid base64-encoded string: number of data characters (113) cannot be 1 more than a multiple of 4`

**Solution:**
* It would be better to let the user know about the error than to let them mass mail corrupted image element.
* This can be done and handled by a try and except statement when the image element  added is not proper.

Sentry-6495526846

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

Foreign key error occurs when a cron job deletes a `withhold (transient model)` 
still linked to a `withhold.line`. The error appears in the terminal, not the UI. 
To reproduce, ensure withhold records in `l10n_ec_wizard_account_withhold` are 
old enough to be removed by `Auto-vacuum`.

Refer to [this](https://github.com/odoo/odoo/blob/e062c9b5773ed0710503c13627e60f8233fcd0a5/odoo/models.py#L7493C1-L7493C87) to understand how transient models are cleaned by the `Auto-vacuum` process.


**Steps to reproduce:**
* Install `l10n_ec_edi` and `accountant`
* Change company to `EC company`
* `Accounting>Customers>Invoices>New`
* Confirm invoice with customer as `EC company` and `Payment method (SRI)` as 
  Credit card
* Add Withhold > Set document number to `001-001-123456789` > Add withhold lines
* `Create and Post`(error will occur when cron tries to delete transient model transient model after
  couple of hours.)

`psycopg2.errors.ForeignKeyViolation:update or delete on table 'l10n_ec_wizard_account_withhold' violates foreign key constraint 'l10n_ec_wizard_account_withhold_line_wizard_id_fkey' on table 'l10n_ec_wizard_account_withhold_line'`

**Solution:**
* Unlink withhold lines first and then let normal unlink take place.

**Sentry-6253783256**

**Steps to reproduce:**

- Installed industry_fsm (Field Service) module
- Navigate the menu Field Service -> Configuration -> Project
- Create a new project
- Then Navigate the menu My Tasks -> Tasks
- Create a new task with the new created project
- Then using the keyboard shortcut ctrl + k for command search, an error occurs

**Cause:**
- When the `stage_id` statusbar had no possible values,
`this.getAllItems()` returned an empty array.
- The command `isAvailable` unconditionally accessed
`this.getAllItems().at(-1).isSelected`, which is undefined,
causing a crash.[see](https://github.com/odoo/odoo/blob/17.0/addons/web/static/src/views/fields/statusbar/statusbar_field.js#L147-L148)

**Fix**
- Add safe check in the command action so it does not attempt
to select a non-existent "next" item.

**Result**
- The command palette no longer crashes when the `stage_id` field has no
available items. Instead, the command is simply unavailable.

opw-5084130
upg-3130405


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#227440

## [FIX] l10n_cz: prevent error with misaligned accounting date and sequence number of demo moves

#### Description of the issue/feature this PR addresses:
Editing CZ Company address while having demo data throws Validation Error

#### Current behavior before PR:
When trying to change address of CZ Company while l10n_cz with demo data is present an error popup is displayed and it's not possible to to save the changes. Steps to reproduce:
 - Install l10n_cz with demo data
 - Open CZ Company in form view
 - Change address (e.g. change city Praha -> Brno)
 - Click Save

#### Desired behavior after PR is merged:
The address changes are saved without any error.

#### Solution:
This change adds `taxable_supply_date` date values for CZ demo moves that are compatible with `invoice_date` values to make sure that accounting date values are the same on each recomputatation and do not lead to new sequence numbers that are not aligned with the previous ones which would cause errors being raised by sequence mixin.

Related to: #226152







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

**Before**
- the active_test context key is part of the main base_automation
  action (base_automation_act), but this context key stays in the
  context further, leading to unwanted filtering in i.e. the
  action_server_ids.resource_ref search view dialog.
- Steps to reproduce:
  - have base_automation installed
  - create an automation rule targeting the res.users model
  - add an Update server action targeting the Partner field
  - in the resource_ref autocomplete, click on Search More...
  - the search view dialogs displays archived records

**After**
- we chose to instead have a default filter in the base_automation_act
  action to include archived records by default. As the context key
  to activate the default filter starts with 'search_default_', it
  is already cleared from the context when opening the form view
  (standard behavior).
- when you reproduce the same steps as before, the archived records
  are no longer displayed in the search view dialog.

**Additional Note**
This fix requires to upgrade the base_automation module.

opw-4886487

This PR addresses an issue where trashed files in documents would still appear when clicking on 'search more' when searching for documents.document in a scheduled action's action. The issue is that the base_automation_act view sets active_test context to False. This context is propagated to view_base_automation_form and results in the context for the field action_server_ids to be active_test = False. The fix for this issue will just be setting active_test to True for the action_server_ids field. This will make it such that the 'search more' action will no longer display anything archived but archived automation rules will still be displayed which was probably the original intention of setting active_test to False in base_automation_act.

Steps to reproduce bug on empty DB:
1) Install base_automation and documents modules.
2) Create a new automation rule targeting the documents module. Make sure to add a trigger.
3) Click on 'Add an action' in the page 'Actions To Do'.
4) In the wizard under action details, set the targeted field to 'folder' (folder_id). Leave the action as 'Update'.
5) Click on the 'Choose a value' drop down.
6) Click on 'Search more'.
7) Notice the number of documents that show up. The numbers on the top right hand side of the wizard should be 1-y/x where x is the total number of documents.
8) Go to the documents module and select any document.
9) Move the document to the trash with the actions button.
10) Repeat steps 4-7. Notice how the number of documents did not change.

Behavior after bug fix:
Upon completing step 10 of steps to reproduce on empty DB, the number of documents will be one less than what it was originally since we trashed one of the documents.

task-4886487


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

**Steps to Reproduce:**
1. Create a new membership product from the Membership module.
2. Open any partner and go to the Membership page.
3. Click on Buy Membership and select the created product.
4. Click on Invoice Membership.
5. Open the newly created draft invoice.
6. From the invoice line, open the product form (via the internal link).
7. Disable the Can be Purchased option and return to the invoice using breadcrumbs.
8. Add a new line in the invoice and search for the same product by its name.



**Observation:**
1. When Can be Purchased is enabled on the product, the product appears in the invoice line search.
2. When Can be Purchased is disabled, the product no longer appears in the search.



**Issue:**

In the product field domain defined in
https://github.com/odoo/odoo/blob/9ba5b41ef0252f4421ff6cdcd7c047b7c53706f4/addons/account/views/account_move_views.xml#L1022-L1029 the `default_move_type` context is `null`.
As a result, only the condition `[('purchase_ok', '=', True)]` is applied in the `name_search` domain.



**Solution:**

Pass the proper context value in the invoice action, ensuring the domain evaluates correctly and the product remains searchable.




**Note:**

The domain used in the following field
https://github.com/odoo/odoo/blob/9ba5b41ef0252f4421ff6cdcd7c047b7c53706f4/addons/account/views/account_move_views.xml#L1022-L1029

is evaluated by a following JavaScript function
https://github.com/odoo/odoo/blob/9ba5b41ef0252f4421ff6cdcd7c047b7c53706f4/addons/web/static/src/core/py_js/py_interpreter.js#L483-L489

rather than on the Python backend. Because the domain logic depends on dynamic
context evaluation performed client-side, there is no straightforward way to
retrieve or test the domain arguments dynamically within the `name_search`
method on the server. As a result, it is not feasible to write automated test
cases for this specific domain filtering scenario in the backend.



opw-5028789

Forward-Port-Of: odoo/odoo#225230