WIP: Reduce swagger docs boilerplate annotations

[mtac50]

What

Link to story

Describe what you did and why.

Checklist

Before you ask people to review this PR:

• Tests should be passing: ./gradlew test
• Github should not be reporting conflicts; you should have recently run git rebase main.
• Avoid mixing whitespace changes with code changes in the same commit. These make diffs harder to read and conflicts more likely.
• You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
• You should have checked that the commit messages say why the change was made.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[stone-dj]

Changes look good, it's always great to see a reduction in duplicated boiler plate code!

Once merged in we need to ensure the wider development team/reviewers are aware of these annotations and use them for any new dev. We also need a strategy to apply this standard across the whole MAAT API project.

[lkm0287]

The existing potential responses above show that HTTP 400 and 500 could be returned however this change makes the only expected response HTTP 404 (not previously an expected response). This seems to be changing our API documentation as well as removing boilerplate code?