CCM-13476 Process print supplier statuses

[Ian-Hodges]

Description

Pickup and transform supplier-api letter status events to digital-letters print.letter.transitioned events.

Context

Currently reporting will need the status of the letters that are sent to the supplier-api. Other consumers may want to subscribe to them too.

Test evidence

Valid supplier-api status event received.

Event sent.

Event seen in the event bridge logs. Also the resulting print.letter.transitioned events.

Note that the end of the origin.subject property has been translated to the messageReference.

Invalid supplier-api status event received.

Event sent.

Event ends up in the DLQ.

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming
• If I have used the 'skip-trivy-package' label I have done so responsibly and in the knowledge that this is being fixed as part of a separate ticket/PR.

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

[nhsd-angel-pastor]

tiny comment in test