Is your feature request related to a problem? Please describe.

Currently, there is no robust way to inject request_id using CDI. Approaches such as the following has been used in code.

However, they only work for REST calls.

Describe the solution you'd like

As suggested by @dimas-b in https://github.com/apache/polaris/pull/3414/changes/BASE..4b6234774c01f3197f2aa78e79dc5d5cbe488ba7#r2692150954,

Please see how TaskExecutorImpl deals with realm IDs. A similar CDI pattern is probably necessary for request
IDs, except that we may not have to produce a request ID for background tasks. I do not have an opinion on whether request IDs should be propagated from REST requests to related async tasks or not. However, CDI must be solid and not cause runtime exceptions even if the request ID is not propagated.

Create a CDI pattern to inject request_ids.

Describe alternatives you've considered

Approaches tried so far include using REST context or SLF4J logging MDC, but both have their shortcomings.

Additional context

No response