[FIX] stock: symmetric reserve and unreserve

When an internal locations has its `scrapped` field set to True,
reserving will increment the quant's `reserved_quantity` while
unreserving will bypass the reservation mechanism (as in a supplier
location). This leads to a desynchronisation between the
partially_available/available move lines and the quant's
`reserved_quantity`, leading later on to "cannot unreserve more than
available" errors.

To prevent this kind of issues, there's a `should_bypass_reservation`
method set on the location that we *should* use everywhere, it was
implemented by [0]. Sadly, this line was not adapted since its
implementaton in [1].

Co-authored by len-odoo <len@odoo.com>

opw 1837900

[0] e1cea2640fc064a56b0dba4f79e6b8a91a48b4fc
[1] 0469d2e7126c46e019ed5f4233ef7b20d3499a0e

0 files changed, 0 insertions, 0 deletions