Notifications from the "Subscriptions Usage" app are deduplicated using SubscriptionsDeduplicationConfig.java.

When a Notifications Admin (RBAC role) configures the required settings to be notified about the "Subscription threshold exceeded" event type, they might not receive any notifications until the next month because new events received after the configuration is done will be considered as duplicate of past events from the current month.

We want customers to be notified as soon as an event is received after they configured the Notifications settings.

Acceptance criteria:

• A new "will_be_notified" boolean field (name to be confirmed) is added to the deduplication key for Subscriptions.
• The value of that field is based on whether the org has a link between the event type and integrations. The existence of recipients can also be considered as an extra condition.
• Caching (local or remote) might be needed to lower the pressure on the DB depending on how often each org receives events.