After the deduplication logic change from notification side, we need to change the payload that we send to the notification topic.

The change should reflect the expected new mechanism introduced from notification side (e.g. a new field in the JSON).

This will enable/disable deduplication logic arbitrarily. A feature flag could be introduced to control this behavior in swatch-utilization. In production the feature flag MUST stay disabled for the moment.

Acceptance criteria:

• We can control deduplication logic without any intervention on notification backend
• We can control deduplication logic with ease (e.g. through the feature flag)
• The default behavior is "deduplication enabled"
• Document necessary key points to help test implementation