Logs handling improvements

[ORybak5]

What

Logs handling improvements

Why

Logs are critical for debugging and all kinds of investigations. A well-designed logging strategy makes it easier to diagnose issues, understand application behaviour, identify root causes, and reduce the time needed to resolve incidents.

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

[github-actions]

• Surviving mutants in this change: 1
• Killed mutants in this change: 20

class	surviving	killed
🧟uk.nhs.adaptors.gp2gp.common.utils.LogSanitizer	1	20

See https://pitest.org

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