Arvados

This is a rename of header which was implemented in #10029.

What was client_session_id/current_request_id should instead use the (semi-)standard X-Request-ID header. If a request ID has already been generated by an upstream component such as a proxy, firewall, or load balancer, that request ID should be reused.

This may be able to use the standard Rails module to do this ActionDispatch::RequestId

For downstream requests, the same request ID should be propagated unless multiple child requests are going to be made to the same server in which case a unique ID for each request can be created by appending an unique suffix to the upstream request ID.

An NGINX article which describes the motivation for this and how to configure NGINX for it is available here:
https://www.nginx.com/blog/application-tracing-nginx-plus/