When integrating Kafka consumers with reactive OAuth2 for securing outbound HTTP calls, a common pitfall arises: Kafka processing typically operates in a background, non-HTTP context. This means there's no `ServerWebExchange` available, which is a core component of the reactive web stack that exposes the current HTTP request/response and request-scoped attributes...