invalidate cache after price edit

_Originally: https://github.com/virge-io/pricelist-frontend/issues/195_

check if we invalidate correct after crud actions on prices endpoint (kassa code stuff)

Not sure if it's needed on create -> when you use the new kassa code it will invalidate correctly.

Update will need it, for sure. Probably good to check the other endpoints also: edit categories, delete prices etc.

Start by tracing cache invalidation for the prices endpoint, focusing first on the update action and the existing kassa code behavior. Then compare create, category-edit, and price-delete actions; done means each CRUD action invalidates the correct cache, with the create behavior confirmed rather than assumed.

Scritto dal modello di indicizzazione a partire dal testo della issue.