Currently, if we try to update the existing `l10n_it_edi_attachment_file` with the signed data received during the submission of an invoice (Invoices for Italian Public Administration businesses must be signed, handled on the IAP side), it fails.

The problem is that in this specific flow, the 'attachment' variable contains a binary rather than attachment_data.

Unfortunately, I could not find a complete flow to reproduce the issue, as there is no flow that sends an invoice to SdI while the l10n_it_edi_attachment_file variable is already set in the move, except maybe via manual import of an attachment into the invoice.

Expected flow:
- User creates a move with `l10n_it_edi_attachment_file` (unspecified how)
- User sends the move to SdI for a Public Administration partner
- IAP signs the attachment and sends it back to Odoo
- Odoo raises an error because it tries to use dictionary features on a binary field
- Odoo does not save the transaction ID, and if the user tries to resend the move, a Duplicate Error occurs from the SdI side.

Ticket [link](https://www.odoo.com/odoo/project.task/5954645)
opw-5954645

Forward-Port-Of: odoo/odoo#253459
Forward-Port-Of: odoo/odoo#252966

Steps to reproduce:
--------------------------------
1. Install Subscription module
2. Create a new subscription quotation and confirm it
3. Generate an invoice for the subscription
4. Attempt to cancel the subscription
   * A ValidationError is correctly raised
5. Close the subscription by selecting any close (churn) reason
6. Attempt to cancel the same closed subscription again

Observation:
--------------------------------
The subscription is successfully cancelled even though it already has invoices

Issue:
--------------------------------
In the following code:
https://github.com/odoo/enterprise/blob/9e39b4b85fcb9f6ed5b21b942796b76b8a6eefdb/sale_subscription/models/sale_order.py#L741-L742 The cancellation logic does not check whether a subscription is already churned and still has active invoices

Solution:
--------------------------------
Added an additional condition to prevent cancelling churned subscriptions that still have active invoices

opw-5479719

Forward-Port-Of: odoo/enterprise#109755
Forward-Port-Of: odoo/enterprise#106596

Steps to Reproduce:
1. Open the website module.
2. Open the media upload dialog to upload an image by either
double-clicking the logo or replacing the existing image.
3. Upload a large file.
4. Abort the upload before it finishes by clicking the 'Discard'
button in the media dialog box.
After performing these steps, a traceback is observed.

Before this commit:
- Image upload failures would throw uncaught exceptions.
- These exceptions would interrupt the flow and result in a poor user
experience with no clear feedback.
- Even after clicking the discard button the image was still
getting uploaded.

After this commit:
- Uploads can be safely aborted when the media dialog is discarded.
- Ongoing XHR requests and RPC calls are properly cancelled.
- The upload loop stops immediately when an abort is triggered with
no traceback.
- Users get a predictable and clean exit instead of a broken state.
- Files are no longer uploaded after clicking Discard.

### task-4752497

Forward-Port-Of: odoo/odoo#250065
Forward-Port-Of: odoo/odoo#219081

[FIX] planning_field_service: fix follow-up (round 4)
This commit continues to fix the various issues found due to the
refactoring of Field Service feature to integrate it into planning
instead of being an extension of project.

This commit will:
- fix 'Print' action and ticket to intervention portal access
- always display in range mode for planned dates in planning.slot view
- update billable and non-billable filters to take into account
  `under_warranty` field
- review search view of planning.slot, some filters have been renamed
  and moved.
- use employees instead of resources in portal list (no need to display
  the material resource in the portal views in other words)
- add "Send mail", "Send SMS", "Send Report" and "Add/Remove followers" buttons
  in cog menu of list and kanban views of planning.slot model.
- remove helper in ticket button since it does not bring useful
  information.
- add ticket description on related shift, when the user plans an
  intervention from a helpdesk ticket, the new shift created from that
  action, will have the description of the related ticket inside Note
  field (name field)
- fix display_name, to avoid displaying the field used in the group by
  in the display name since it is a bit redundant
- take into account worksheet set in product as default
- fix some labels, visibility conditions, dates format, group_expand
- add default company of the slot when the user creates a resource from
  the form view of planning.slot model
- show customer preview stat button once the intervention is completed
  and a report is available for that intervention
- update tooltip for employee product to bring more context to explain
  how that new field works.
- make sure the SOL for timesheet is not generated when we complete an
  intervention if the project linked is non billable
- add icon on stat button of timesheet
- make sure the user can only create service product in product field in employee
- show "X Products" button to non sale user in the form view of
  planning.slot
- make project billable and timesheetable by default when the user wants
  to create a new project from the project_id field inside the form view
  of planning.slot model
- hide schedule stat button in the form view of project.task if the task
  is a template or linked to a project template
- update visibility condition of sign in in calendar, to make visible
  for planning manager when the slot is published even if the shift is
  not assigned to that user and the slot is in the past.

task-6009593

**Problem:**
the default account suggested for landed cost (with 
real time category) are not the good ones.

**Steps to reproduce:**
- create a storable product with perpetual average category
- create a landed cost (a service product with 'is a 
landed cost' checked in the purchase tab)
- create a category for the landed cost with perpetual valuation
- confirm a purchase order for 10 quantity of the product with a 
unit price of 10
- validate the receipt
- confirm quotation for 3 of the product, validate the delivery and 
confirm the invoice
- create a bill for the purchase order
- on the invoice lines, unhide the product column
- add an invoice line with the landed cost product, for a quantity 
of 1 and a price of 10
- confirm the bill
- click on create landed cost 
- select the receipt in the transfers field
- validate
- click on the journal entry on the landed cost form

**Current behavior:**
On the bill, for the landed cost : 
- stock valuation is debited of 10
- account payable is credited of 10 (which makes the total 
credit 110 for account payable)

On the journal entry linked to the landed cost: 
- stock valuation is debited of 7 
- stock valuation is credited of 7

So in total there is a debit of 10 in stock valuation and 
a credit of 10 in account payable.
Which does not reflect that part of the products are out 
of stock. 

**Expected behavior:**
If the expense account was used, both on the bill and on 
the landed cost, (which is already the case for landed cost
with periodic category) the account move lines would be: 

On the bill : 
- Expense is debited of 10
- account payable is credited of 10 (which makes the total 
credit 110 for account payable)

On the journal entry linked to the landed cost: 
- stock valuation is debited of 7 
- Expense is credited of 7

So in the total there is : 
- a credit of 10 in account payable
- a debit of 7 in stock valuation
- a debit of 3 in expense

This is what we want, because the debit of 7 in stock valuation 
reflect that we only increase the valuation by 7 because only 7 
products are still in stock. 
The debit of 3 in expenses compensate for the cogs. Indeed 
when we invoiced the SO, the cogs where of 30 but, after the landed
cost, valuation wise, the products actually exited the stock with a 
value of 33 total (11 each).

**Cause of the issue:**
For the bill: 
when you create the new account move line and enter the product, 
_compute_account_id is called to compute the default account 
for the line. 
In the stock override, _eligible_for_stock_account is called on the line
https://github.com/odoo/odoo/blob/3542c542eac5b204e69a8dd6ae1907cfcef60af3/addons/stock_account/models/account_move_line.py#L18-L19
Because of the stock_landed_costs override, the return value is true
https://github.com/odoo/odoo/blob/3542c542eac5b204e69a8dd6ae1907cfcef60af3/addons/stock_landed_costs/models/account_move.py#L78-L82
So the account is changed to stock valuation
https://github.com/odoo/odoo/blob/3542c542eac5b204e69a8dd6ae1907cfcef60af3/addons/stock_account/models/account_move_line.py#L23-L24

For the landed cost: 
- if we create it by selecting 'create landed cost' on the bill : 
the account id is set in button_create_landed_cost
https://github.com/odoo/odoo/blob/3542c542eac5b204e69a8dd6ae1907cfcef60af3/addons/stock_landed_costs/models/account_move.py#L34
-if we create the landed cost, from adjustment/landed cost and 
selecting new : the expense account is already selected


**fix:**
In both cases, the client can already manually set the 
accounts they want, the fix is about having the right 
default accounts. 

opw-5941753

Forward-Port-Of: odoo/odoo#253430
Forward-Port-Of: odoo/odoo#251766