Ability to combine outbox messages

[trevoryager-callaway]

If there are multiple outbox messages that have the same group id, application, message definition and subscription, AS WELL AS always needing to send the most up-to-date information of a specific record via the use of a resolver, then lets give a configurable checkbox to combine all of those callouts down to 1 and then we will mark all of the outbox messages and related subscriptions as having passed.

[ChuckJonas]

I discussed this in #10 (second point). Although I think it makes sense to track in a separate issue.

I'm still not 100% on the best way to go about this...

The "Checkbox" option ("Deduplicate Outbox Messages with the same GroupId for this subscription") could work but kinda feels like it is "overloading" the functionality of the Group.

What if we also included the Message "Payload" (Outbox_Message__c.Message__c) in the check?

Configuration would look something like this:

• Deduplicate Similar Messages: When checked, "active" messages with the same Payload & GroupId will only be relayed once per subscription. All matching Subscription Outbox records will be updated based on the result of the single relay.

We could then just keep track of a map of ${subscription}-${groupid}-${payload} -> RelayContext for any subscriptions where this is configured. If we encounter a match, then we can just copy the attempts and completed status from the context and add it to the finalizer without actually running a Relay Client