[16.0] [FIX] stock_picking_report_valued_sale_mrp: fix components per kit computation when redelivering

[rrebollo]

Fixes #451

This PR contains two commits:

1. Adds a test that reproduces the issue.
2. Introduces a proposed fix for the issue.

🧩 Context

The problem occurs in the following workflow:

1. Sell a kit.
2. Confirm the Sales Order (SO).
3. Validate the related picking.
4. Return the picking.
5. Cancel the SO.
6. Set the SO back to draft.
7. Confirm the SO again.

At this point, the system generate another picking and you validate this too, and we noticed that the kit component quantities shown on the delivery slip report were incorrect.

🔍 Root Cause

The issue appears to stem from the calculation of the component quantities per kit during this sequence of operations.

🛠️ Proposed Fix

This PR provides an initial attempt to resolve the incorrect quantity computation. Additional details and discussion can be found in the linked issue.

HT14789
@BinhexTeam

[OCA-git-bot]

Hi @chienandalu,
some modules you are maintaining are being modified, check this out!

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[JordiMForgeFlow]

code LGTM 👍🏼

[GuillemCForgeFlow]

code LGTM 👍🏿

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[rrebollo]

@rousseldenis could you merge this one?

[BhaveshHeliconia]

LGTM!

[rrebollo]

@pedrobaeza could U merge this one?

[pedrobaeza]

Don't introduce extra empty lines inside methods, and please reduce AI usage to the minimum, as the code is bloated due to it.

[pedrobaeza]

Instead of complicating this way, just sum the proper moves.