[19.0][ADD] product_pricelist_item_uom_standard

[Ricardoalso]

Add a backport of Odoo 19.3's native pricelist-rule-by-UoM feature (odoo/odoo@d2648b1d9839), restricting pricelist item rules to a specific product packaging.

OCA/product-attribute already ships product_pricelist_item_uom, but it defines uom_id on product.pricelist.item as a computed field always defaulted to the product's base UoM, and it never filters rule selection. The two modules are declared mutually exclusive via the manifest excludes key.

[ivantodorovich]

Thanks!

I'm not sure we want to keep both product_pricelist_item_uom and this one.
I'd be more inclined to have this one replace the existing product_pricelist_item_uom, consuming its name, given it's essentially the same feature -- but this one is aligned to what's implemented in standard in 19.3 (and future 20.0)

ping @JordiBForgeFlow @rousseldenis @monen17

[monen17]

I'm not sure we want to keep both product_pricelist_item_uom and this one.

I agree it's better to avoid excludeing modules.

I'd be more inclined to have this one replace the existing product_pricelist_item_uom, consuming its name, given it's essentially the same feature -- but this one is aligned to what's implemented in standard in 19.3 (and future 20.0)

I'd rather go with the REF commit you suggested in #2308 (comment) so the commit history of product_pricelist_item_uom is preserved and we can see how its logic changes/gets migrated.

[Ricardoalso]

Thanks!

I'm not sure we want to keep both product_pricelist_item_uom and this one. I'd be more inclined to have this one replace the existing product_pricelist_item_uom, consuming its name, given it's essentially the same feature -- but this one is aligned to what's implemented in standard in 19.3 (and future 20.0)

ping @JordiBForgeFlow @rousseldenis @monen17

I'm not sure we want to keep both product_pricelist_item_uom and this one.

I agree it's better to avoid excludeing modules.

I'd be more inclined to have this one replace the existing product_pricelist_item_uom, consuming its name, given it's essentially the same feature -- but this one is aligned to what's implemented in standard in 19.3 (and future 20.0)

I'd rather go with the REF commit you suggested in #2308 (comment) so the commit history of product_pricelist_item_uom is preserved and we can see how its logic changes/gets migrated.

Thanks for the follow-up on this! I like the option of pushing a REF commit ([REF] product_pricelist_item_uom: backport from odoo 19.3) on top of product_pricelist_item_uom, as it would indeed preserve the commit history.

I will rebase my work on ForgeFlow:19.0-mig-product_pricelist_item_uom and rework this PR if there is consensus among the contributors.