feat: Implementation of RFC9457

[doddi]

What's the problem this PR addresses?

Http1.x has a reasonPhrase for conveying extra information about the reason for a given status code. This was often useful for adding additional context for why a response has failed, for example a generic 403 status code can have many interpretations.
Http2 onwards no longer has reasonPhrase as part of the protocol and as such is difficult to convey additional context.

RFC9457 adds the ability to convey this information as part of the body, indicated using a header 'application/problem+json'
There is prior art in client tools, see the recent maven implementation here

...

How did you fix it?

There is a customPackageError call the determines if any unique messaging should be part of the response. Here I check for the existence of the 'application/problem+json' header, if the header exists and there is valid json body then a RFC9457 report is generated.

Example output:

➤ YN0035: │   RFC9457: "{\"status\":403,\"title\":\"Component Report\",\"detail\":\"Requested item has been blocked, FOR DETAILS SEE ------>>> http://localhost:8070/component-report/NWJiMWMyN2EzZjVjNDYxYWE2NWY0ODk3NDAxNWVjMDY <<<------\"}"

...

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.