validate Mhs Queue properties

[Jonopono123]

What

Added validation around MHS Queue Config Variables

Why

If these are not provided, typically the terminal spits out a verbose and potentially convoluted message, which would be much more useful if it simply pointed at the missing variables.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Internal change (non-breaking change with no effect on the functionality affecting end users)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have updated the Changelog with details of my change in the UNRELEASED section if this change will affect end users
• A corresponding change has been made to the Mapping Documentation repository

[github-actions]

• Surviving mutants in this change: 10
• Killed mutants in this change: 0

class	surviving	killed
🧟uk.nhs.adaptors.pss.translator.validation.MhsQueuePropertyValidator	10	0

See https://pitest.org

• Arcmutate licence valid until 2026-07-16 (yyyy/mm/dd) (non-commercial use only)
• Project uses Spring, but the Arcmutate Spring plugin is not present.

[github-actions]

Images built and published to ECR using a Build Id of PR-960-ce58f14