### Issue:
It is possible to break the followup reports by directly creating entries in the past.

### Steps to reproduce:
- Example on Belgian loca
- Accounting Dashboard > Misc > new Entry with
	- Date far in the past (ie 2024-01-01)
	- Account: "400000 Customers", Partner: "test partner", Debit: 500.0
	- Account: "499000 Suspense Accounts", Credit: 500.0
- Post
- In Customers > Follow-up reports, the partner is marked as "In need of action" even if no due date was specified
- Accounting Dashboard > Bank > new with Amount: 500.0
- "Save & Close" then click on it
- In the page "Manual Operations" change the partner to the one from the MISC entry
- Change the Account to "400000 Customers"
- Validate
- The follow-up report is no longer "In need of action"
- Create an invoice with a due date in the future
- The follow-up report is back to "In need of action" with the amount of the invoice
- When sending the follow-up, the Customer statement reads "your account shows an outstanding balance of 0.00€"

### Cause:
The origin of this issue is that the MISC entry and the Bank payment are not reconciled. The MISC entry is used to calculate the state of the followup making it to "In need of action" but the bank entry is balancing the amount to 0.00€.

The MISC entry should not be used to compute the followup state as it has no due date specified (it makes no sense, it is never linked to any invoice). But in the code when there are no `line.date_maturity` we fallback on `line.date`.

### Solution:
The lines without due date or payment term should not be used to compute the state of the followup or calculate the total due.

So we remove the fallbacks on `line.date` when `line.date_maturity` is False. Some tests needed to be adjusted as they were not using any payment terms or due date. They were working because of the fallback on `line.date`.

opw-4784250

Forward-Port-Of: odoo/enterprise#89627
Forward-Port-Of: odoo/enterprise#87873

### Steps to reproduce:

- Configure the sendcloud delivery method (for instance with Bpost @home for a belgian company) and enable the `Use Batch Shipping`` option on the delivery method.
- Create a storable product with a weight of 1 kg and a positive volume.
- Create and confirm sale order for 4 units
- Add shipping -> chose sendcloud
- Separate the delivery of 4 kg in 3 packs:
    - set quantity to 1 -> put in pack
    - set quantity to 2 -> put in pack
    - set the quantity to 4 -> put in pack
- Try to validate the delivery
#### > invalid operation:  weight: "A valid integer is required."

### Cause of the issue:

Sendcloud's api only accept integer values for the weight: 
![api](https://github.com/user-attachments/assets/7080094f-debd-4620-84e6-63e97e868508)

However, to evaluate the price of the parcel accurately for a batch shipping we need to compute the average weigth to provide to sendcloud. Converted to grams we tehrefore provide a value of 1333.333333 to sendcloud which raises an invalid operation:
https://github.com/odoo/enterprise/blob/72b4a223ec4e2e09fc93bebd150923abba37a8df/delivery_sendcloud/models/sendcloud_service.py#L378-L379 https://github.com/odoo/enterprise/blob/72b4a223ec4e2e09fc93bebd150923abba37a8df/delivery_sendcloud/models/sendcloud_service.py#L205-L207 https://github.com/odoo/enterprise/blob/72b4a223ec4e2e09fc93bebd150923abba37a8df/delivery_sendcloud/models/sendcloud_service.py#L44

opw-4874063

Forward-Port-Of: odoo/enterprise#89495

**Current behavior:**
Using the UPS rest connector and trying to process a delivery to
a Mexico-based customer will fail with error code:
`121984 - A package in a Mexico shipment must have a Merchandise
Description.`

**Expected behavior:**
Can process shipment.

**Steps to reproduce:**
1. Create a UPS rest delivery option

2. Create an SO for some product to a Mexico-based client, add
the UPS delivery, confirm, try to validate the delivery -> 400

**Cause of the issue:**
For non-return shipments, the description in the Package object
is `None`, but when the receiver is based in Mexico, this field
is required.

**Fix:**
Create a package level description based on the one added here:
https://github.com/odoo/enterprise/commit/a7b8673364e0ac626bcc8ded72501c4f2866564c

To the UPS API spec here: https://developer.ups.com/tag/Shipping?loc=en_PE&tag=Rating#operation/Shipment!path=ShipmentRequest/Shipment/Package/Description&t=request

opw-4508139

Forward-Port-Of: odoo/enterprise#86411

Steps to reproduce:
1. Connect IoT Box and any printer that accepts PDF
2. Turn on Reception Report option on Inventory Settings
3. Set configuration of Receipts to print out Reception Report and Label
4. Assign Reception Report and label to the printer
5. Create a PO and run through the Reception process (PO > Reception of Delivery)
6. Validate the Reception of the order

-> Result:
   Odoo will prompt the customer to select a printer, however we are not able to choose a printer in time as the process continues without selecting one. This in return does not send the report to the printer via IoT.

The root cause of this bug is that the IoT report handler JS function returns too early, it resolves once the printer selection popup has appeared, instead of resolving once the printer has actually been selected and is starting to print. Therefore the multi-report printing code assumes the print is done and triggers the next print, which causes the popup to close before the user can select a printer.

To solve this bug, we listen for a 'printer-selected' event in the handler, and resolve only once we have received this event. This fixes the flow, allowing a printer to be selected for each report that is being printed in sequence.

opw-4790299

Forward-Port-Of: odoo/enterprise#89617
Forward-Port-Of: odoo/enterprise#88538