[FIX] purchase_mrp, sale_purchase_stock: track kit bom when receiving without pull rule

Problem:
If an inventory workflow is completed without any pull rules (only Push or Buy), then `bom_line_id` is never set on the sale order line. The result has two primary impacts: `qty_received` will not be updated upon final transfer, and the COGS line on the invoice will be calculated using the incorrect method, with an incorrect result.

Solution:
Upon confirming a Purchase Order, when the picking is being created, we will try to assign the `bom_line_id` on the Sale Order Line if:
	1. The PO is attached to a Sale Order
	2. The SO line is for the kit
	3. The product on the PO line is component of the BOM for that kit
With the `bom_line_id` assigned on the SO line, `qty_received` will be calculated correctly for kits, and COGS lines on the generated invoice will also be calculated correctly based on the kit.

Steps to Replicate (Runbot 18)
- 2-step receipt, 2-step delivery
- Cross-Dock enabled
- Kit item, fifo auto
	- No routes enabled on kit
	- Two components, fifo auto
		- Enable Buy and Cross-Dock routes
		- Set a vendor and non-zero price

1. Create a sale order for the kit and sell for non-zero price, confirm
2. Confirm the PO
3. Validate the pickings
	1. Receipt
	2. Cross-Dock
	3. Delivery
4. Go back to the sale order, note the first issue of 0 quantity delivered
5. Create an Invoice
6. Confirm the invoice, note the second issue of the COGS lines being triple the total purchase price

opw-5139590

Forward-Port-Of: odoo/odoo#235818
Forward-Port-Of: odoo/odoo#233132

This commit fixes various issues when using Viva Wallet, including the following:
- When two Viva Wallet terminals had a payment in process at the same time in the same POS, one of the payments would fail on Odoo even when it succeeded on the terminal.
- When a previous Viva Wallet payment was stuck (never completed or failed), trying to make a new payment would mistakenly affect that previous order instead of the new order.
- When refreshing the page during a payment, it becomes stuck and never confirms or fails.

To fix these issues, there are two main changes:
1. Stop using the `getPendingPaymentLine` method to retrieve the Viva Wallet payment line. This method is flawed as it assumes there is only one pending payment at a time.
2. Store the Viva session ID for a payment in the payment line's UI state, instead of on the plain JS object. This allows it to persist after a refresh.

opw-5226966
opw-5248178

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

Forward-Port-Of: odoo/odoo#236004
Forward-Port-Of: odoo/odoo#235695