Add ID to trace jRPC calls

[arnaubennassar]

Take the ID from X-Request-ID http header

• Add id in the logs
• Add id in the executor (need changes on gRPC)

[tclemos]

Here is the rationale behind this issue and some suggestions to achieve it.

Basically, we want to track logs e2e of a specific request by having a unique ID across logs between components.

Even though X-Request-ID is the most common way to identify HTTP requests, this header is optional and unofficial, also it depends on the client providing it, which means requests without it will continue to not have the logs identified. more details here: https://http.dev/x-request-id

On another hand, the JSON RPC Request has a field called ID which is meant to be used by the client to correlate the responses with the requests, I also think this is not what we are looking for. more details here: https://www.jsonrpc.org/specification#request_object

My suggestion is that the jRPC tries to get the X-Request-ID header, if it was not provided by the client, the jRPC itself automatically generates a unique ID for the request, like a Prefix(so we know this was automatically generated) + UUID(https://en.wikipedia.org/wiki/Universally_unique_identifier) to be able to safely generate them across all the jRPC instances.

After that, the jRPC sets the ID to the Go context(https://pkg.go.dev/context#WithValue) that is provided for all the calls within this request, and when a GRPC connection is needed, we set the header X-Request-ID with the same ID and provide it via CallOptions(which is an optional parameter for each call in a Go autogenerate GRPC client, more details here https://pkg.go.dev/google.golang.org/grpc#HeaderCallOption) for each GRPC call we do.

In order to make it easier to consume, the Context can also contain an instance of Logger already set with the request ID, so we can reuse this instance instead of the default logger.

This will require some changes in the way we handle the jRPC requests and also we must take into account the requests made via WebSockets.

[tclemos]

Take this into account #797

Add Go routine ID to the context logs too

[tclemos]

related #2564