Possible scenarios to get ConstraintViolationException.ValidProductization

Hi there,

I am currently trying to debug the `ConstraintViolationException.ValidProductization` error by first recreating it in the Sandbox environment. Unfortunately, I haven't been able to do so yet. I am using a `PATCH` request on the `/sale/product-offers/:offerId` endpoint to update an active offer.

I have a couple of questions to clarify what triggers this error:

1. It seems like this error should occur when I update an offer, but the product attached to that offer no longer exists in the Allegro catalog. Is that correct?
2. I understand that it is not possible to create a new product using `PATCH` `/sale/product-offers/:offerId`. I assumed that if I tried to update the EAN of an offer's product using this request - and a product with that new EAN does not exist in the Allegro catalog - thus triggering the `ConstraintViolationException.ValidProductization` error. However, this did not happen, the product attached to the offer simply updated with the new EAN, as explained in the [diagrams](https://developer.allegro.pl/tutorials/how-to-process-list-of-offers-m09BKA5v8H3). What am I missing here? What would need to change in my request so that the product is no longer recognized?
3. Could you provide an example scenario where `ConstraintViolationException.ValidProductization` would be thrown? E.g. what kind of `POST` request followed by `PATCH` request would trigger this error?

Dzieki za pomoc!

Start with the PATCH /sale/product-offers/:offerId behavior and the linked product-offer and offer-management tutorials, then review the active issue thread for the intended clarification. Done means documenting a concrete POST-then-PATCH scenario that produces ConstraintViolationException.ValidProductization and explaining the product and EAN conditions involved.

由索引模型根據 Issue 內容生成。