Don't just log but also capture Keycloak exceptions during client creation

[Anahkiasen]

Fixed

• Don't just log but also capture Keycloak exceptions during client creation

---

We seem to be throwing the Exception with the entire response from the API, so I don't think there is that much additional information to log that could help with the error in the screenshot since it seems Keycloak really is just returning "401 Unauthorized" without elaboration.

So this change should at least prevent Keycloak exceptions from not reaching Sentry, as currently they are caught and logged but not released back for capture by Sentry? This will hopefully provide us with a lot more metadata to understand what goes wrong.

Ticket: https://jira.publiq.be/browse/PPF-659

[LucWollants]

@Anahkiasen I guess we need to do this for all jobs because we don't report anything.

But I do wonder why the error method does not reach Sentry, because the default logging stack inside the Laravel logging config file has Sentry included.

[Anahkiasen]

Investigating whether the Sentry log client should also capture by default, the documentation say so but it doesn't seem to be the case, so perhaps it's an issue there, will do some local tests

EDIT: Seems to be when the exception is not present in the logging context which happens since we catch them and only log the message. Passing the exception in the context too allows it to be captured