**Problem:**
For products with variants and differents steps for the BoM depending
on the variant, the Manufacturing Order overview for a given product
with a given variant would display the sum of the cost of all variants
possible for this product. If we had a product "Drawer" with a color
variant "Black" and "White", which cost 10 and 20 euros respectively,
the Manufacturing Order overview of a Black Drawer would display the
cost of the drawer + **30** euros (10+20), instead of being the cost
of the drawer + **10** euros. The display cost is the sum of the price
of every variants for this product, instead of being the price of the
current variant of the product.

**Steps to reproduce:**
- Create a product with variants
- Change the BoM and make some components needed only for certain variants and add a price for them
- Go to the MO overview
- The Cost BoM cost total is the sum of all prices AND variants

**Cause of the issue:**
https://github.com/odoo/odoo/blob/d3ab7b2c3ceddbb4cb8d8e91fac0d60e28e5673a/addons/mrp/report/mrp_report_mo_overview.py#L85
This treats every remaining lines of the BoM as a missing component,
thus adding it's price to the total price. Some lines should only be
applied if a specific variant is selected, but with this code, every
line that has a condition depending on variants will be taken in.

**Fix:**
Before adding the product of a BoM line to the missing components, we
check that the BoM line should be applied to the current variant.
The missing components are still used and can be not empty in the
case where the BoM includes a line that was deleted from the MO,
making the MO cost and the BoM cost different. In this case, the
missing components will not be empty and will still work as
intended without taking the unwanted variants into account.

opw-4557169

When a signed document is moved to trash in the documents app, when the cron tries to delete the said document it should raise a foreign key violation error in the terminal not in UI.

**Steps to reproduce:**
* Install document and sign
* Document App> all> click `Employment contract.pdf`.
* Select sign>drag and drop Signature>Sign now
* Sign the document>validate and send completed document
* Documents>certificate of completion or the signed document>actions>trash
* The error will be produced when cron deletes the document.
* You can delete the document from trash to see what error will be displayed by cron.
  
 `ERROR: update or delete on table "ir_attachment" violates foreign key constraint "sign_request_completed_document_rel_ir_attachment_id_fkey" on table "sign_request_completed_document_rel"`
 
**Solution:**
* Modifying the domain for `_gc_clear_bin` via a new function called overridden `_gc_documents_domain` in `documents_sign` this will allow for cron to skip over signed required document during unlink process.
* This will still throw an `Validation Error` when the user tries to delete it from the GUI letting them know it cannot be deleted.

Sentry-6225030131

**Issue**
In the Mexican localization, the CFDI usage (`l10n_mx_edi_usage`) field is not visible on POS orders in the backend. This prevents users from selecting or modifying the usage when manually generating an invoice from the POS order.

**Steps to Reproduce**
1. Install the Point of Sale app and the Mexican localization (l10n_mx)
2. Complete a POS order without generating an invoice
3. In the backend, go to Point of Sale > Orders > Orders
4. Open the newly created order
5. Notice that the CFDI Usage field is missing

**Root Cause**
The usage field is given a default value at the model level: https://github.com/odoo/enterprise/blob/bc3db24f83473d5646f7c2cfca8ed1c5b064ea2e/l10n_mx_edi_pos/models/pos_order.py#L65-L70 However, this value gets lost during the order processing flow. When an invoice is requested directly from the POS UI, the usage is explicitly set in the `sync_from_ui` method: https://github.com/odoo/enterprise/blob/bc3db24f83473d5646f7c2cfca8ed1c5b064ea2e/l10n_mx_edi_pos/models/pos_order.py#L110-L112 But if no invoice is requested at the time of the order, the usage is not preserved or restored in the backend. 

**Fix**
Explicitly set the CFDI usage to its default value when an invoice is not requested during the POS flow. This ensures the usage field is retained and displayed properly in the backend, allowing users to create invoices manually.

opw-4776487