CCM-13768 Print analyser component

[Ian-Hodges]

Description

Add Print Analyser component.

Context

The print analyser component responds to file.safe events and performs the following:

1. Fetches the pdf file from S3.
2. Determines the page count.
3. Calculates a hash of the pdf.
4. Sends a print.analysed event with these details.

Test evidence

Receipt of file.safe event and routing through to sqs queue.

Receipt of pdf.analysed event with the page count.

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]

it looks good to me. I just wonder whether we want to add a bit of logging for the positive scenario to include like the messageReference or when supporting the app we should be mainly checking the logs from the event bus