### Steps to reproduce:
	- Activate a payment method
	- Create a subscription and preview it in portal view
	- Pay this order through the order's portal view
	- Navigate to the invoice got generated
	- Notice there is not 'Payments' smart button

### Cause:
Since https://github.com/odoo/enterprise/pull/77432/commits/02f72f94b7c996fa19c6bfc70a704d27aa677245 we stopped creating the invoice before the payment and the transaction in the controller and we let _post_process do this invoice creation. So the invoice actually gets created after the payment not before and when preparing the payment values the invoice_ids will be False

https://github.com/odoo/odoo/blob/6c88e6ffd2c906b72b31d3c34ad3d6da5efba204/addons/account_payment/models/payment_transaction.py#L155-L170

Then we create the invoice for the transaction and we don't propagate it to the payment.

https://github.com/odoo/enterprise/blob/20fd574367757c06f30c344056e8b8d91ba8244c/sale_subscription/models/payment_transaction.py#L72-L84

### Fix:
Link the payment to the invoice after creating the invoice and link it to the transaction.

opw-4867631

Forward-Port-Of: odoo/enterprise#91690

The combination of the following recent changes prevented the OCR from filling the name of the expense:
- New expenses are named "Untitled Expense {date}" by default instead of the name of the attachment (see commit odoo/odoo@ca1f644).
- The OCR doesn't override the name if it's not set to the default value (see commit 5c813dc).

The first commit didn't update the default expense name that was used in the OCR code, it was still computed from the attachment name.

After the second commit, the OCR couldn't fill in the name of the expense anymore, since it was expecting the name to be the attachment name, but it was "Untitled Expense {date}" instead.

This is fixed by checking that the expense name contains "Untitled Expense" (and taking translation into consideration).

This commit also improves the tests in multiple ways:
- For the `test_auto_send_for_digitization` test, it now mimicks an upload of the document to force the creation of the expense with the default name, this should prevent this from happening again.
- It now uses an actual PDF document instead of "fake" attachments.
- Minor clean up.

task-[4684825](https://www.odoo.com/odoo/project/967/tasks/4684825)

Forward-Port-Of: odoo/enterprise#92324

### Steps to reproduce:

- Create a storable product tracked by lot
- Create and confirm a receipt for 10 units of that product
- Go to the barcode app and regiter 1 unit
- Exit the picking
- Go back to the picking register the 9 remaining units
- Exit the picking and comeback
#### > The demand of the receipt has been updated from 10 to 19.

### Cause of the issue:

Exiting the picking will launch a call of the `post_barcode_process` in order to keep track of the changes you made without changing the initial demand:
https://github.com/odoo/enterprise/blob/c26c21cec14a234021bb13bbc2684334bc64b70b/stock_barcode/models/stock_move.py#L50-L53 THe first time you enter the picking you have a single move with a quantity of 10. The first time you exit, since you have set a qty_done of 1 (and hence have updated the quantity of the associated move to 1), the `split_uncompleted_moves` will then create a move for a quantity of 9 in order to keep 10 units assigned. The second time you enter the picking both moves are grouped in a single line since the product is tracked by lot, however, when you update the qty_done of that grouped line you will actually only update the quantity of the first move line and its related move. Since the `_truncate_overreserved_moves` was not designed to handle these grouped lines, it does not notice that the combined reservation overcomes the actual demand.

opw-4731803

Forward-Port-Of: odoo/enterprise#91381
Forward-Port-Of: odoo/enterprise#89967

Problem:
The non-recurring products added through upsell Sales Orders are not included in the Sales Analysis Report. This results in missing sales data for those products, leading to inaccurate reporting.

Purpose:
To ensure that non-recurring products added through upsell Sales Orders are correctly included in the Sales Analysis Report (report_all_channels_sales_action). This fix updates the report's domain filter to include upsell orders when the product is not recurring, resolving the issue of missing sales data for such products.

Steps to reproduce the bug:

1. Create a Sales Order (SO):
  Add two products to the order:
    - One recurring product (e.g., a subscription-based product with a recurring billing policy).
    - One non-recurring (standard) product. 
2. Confirm the SO
3. Generate an Invoice for the confirmed SO.
4. Validate the Invoice and deliver the non-recurring product (process the delivery order fully). 
5. Create an Upsell Sales Order:
    - From the original SO, create a new upsell SO.
    - Add the same non-recurring product again. 
6. Navigate to the Non-Recurring Product Page:
    - Open the Product form for the non-recurring item.
    - Click on the "Sold" smart button (shows delivered/sold quantities in the past 365 days).
    - This opens the Sales Analysis Report (report_all_channels_sales_action) filtered by this product.

Issue:
The upsell Sales Order is not included in the Sales Analysis Report for the non-recurring product. As a result, the delivered quantity or revenue from upsell SOs is missing from the report for non-recurring products.

opw-4940977

Forward-Port-Of: odoo/enterprise#92559

Currently an error occurs when trying to run whatsapp marketing automation test more than once.

**Steps to replicate:**
* Install `marketing_automation_whatsapp`
* Setup whatsapp integration
* Marketing Automation > New > Start From Scratch > Add a new activity
* Select Activity Type as Whatsapp Message and a Whatsapp Template
* Launch a Test > Pick a contact > Launch > Run (Do this step twice)

**Error:**
`ValueError: Expected singleton: marketing.trace(6, 4, 3, 2, 1)`

**Cause:**
This error occurs because the variable `trace` contains multiple records, but the `process_event` method is being called on the entire recordset.

Since `process_event` uses `self.ensure_one()`, it expects exactly one record, and therefore raises an error at [1] when multiple records are passed.

**Solution:**
* Handle trace records one by one using a loop.

[1]: https://github.com/odoo/enterprise/blob/624b18bdb5dff0df4756c4e1d37a696631e57a05/marketing_automation_whatsapp/models/marketing_trace.py#L20

**Sentry-6772553612**

Forward-Port-Of: odoo/enterprise#91207

Steps to reproduce:
  1. Go to a WhatsApp template, for e.g. Sale Order.
  2. Update the sample value for the Portal Link variable to include an underscore.
  3. Click on Preview

Issue:
Due to the current regex, we will apply italic to any underscore we find which is not ideal, mostly when we work with URLs that can contain underscores like "acces_token" which we will try to apply italic to it too.

Solution:
Following the most common logic for italic formatting, we will only apply italic formatting when the underscore is surrounded by whitespace. This is the same way it already behaves in Whatsapp.

If we write it like_this_for example, it will not apply italic formatting, but if we write it like this _this_ it will apply italic formatting.

So this for example:
 **"If we write it like_this_for example"**
 Will be like - before the fix:
  **"If we write it like<i>this</i>for example"**
 Will be like - after the fix:
  **"If we write it like_this_for example"**

opw-4720017

Forward-Port-Of: odoo/enterprise#91217