Add error/warn logging when producing ProblemDetails

[osxhacker]

While error responses are properly emitted by the microservices, currently the conditions which result in a ProblemDetails are not being logged via log4cats.

Successful completion of this task will introduce logging which:

• [x] Warns for recoverable problems, such as ObjectNotFoundError and ConflictingObjectsError.
• [x] Errors for all others.
• [x] Must include X-Correlation-ID and subsystem-specific information if available.
• [x] Must emit a log entry if context is not available (i.e., deserialization errors).

[osxhacker]

Introducing a new Advice type named LogInvocation has identified a minimal impact solution which addresses the feature enhancement.

It has been successfully tested locally with TapirEndpoint and what remains is incorporating it into the Aspects involved with Kafka event processing.