[Host.Outbox.Sql] Abort publishing of unknown message types

[EtherZa]

OutboxSendingTask will immediately abort sending a message when the MessageType fails to resolve.

Changes:

• MessageType resolution moved out of SqlOutboxRepository and into OutboxSendTask and OutboxForwardingPublishInterceptor.
• When OutboxSendTask fails to resolve the 'MessageType', an error is logged and the message is flagged as 'DeliveryAborted'.
• When OutboxSendTask fails to resolve the associated bus. The affected messages are also immediately aborted (previously, n attempts would be made before doing the same).

[zarusz]

@EtherZa 2 minor comments added.

Could you please add a note about how a missing message type will be handled to the outbox docs?

Then I am good to merge.

Thanks for your contribution.

[zarusz]

@EtherZa any chance you could increase the coverage on SqlOutboxRepository around the Abort methods and remove the unused variable flagged by Sonar?

[EtherZa]

@zarusz I have resolved the Sonar complaint and pushed the boundary again to get the requested coverage on SqlOutboxRepository by introducing TestContainers -I am assuming that you are keen to move in this direction as per your comment in 277.

Please let me know if you are happy with the approach and I will squash/sign the commit.

[zarusz]

@EtherZa, I appreciate you pushing this over the finish line despite project deadlines!

Yes, happy to merge. Please squash and I am going to release a minor release soon.

Thanks!

[zarusz]

Can you also resolve the conflict, I just merged another PR @EtherZa ?

[EtherZa]

@EtherZa, I appreciate you pushing this over the finish line despite project deadlines!

Yes, happy to merge. Please squash and I am going to release a minor release soon.

Thanks!

No worries. I've rebased and pushed. All should be good to go now :)

[sonarcloud[bot]]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
94.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud