Push the requestID through the whole stack

[micbar]

The requestID is part of the context in the http layer.
In the past, it was pushed further through the stack and was also arriving in the grpc context.

As a consequence, all log lines in ocis were printing out the requestID.

This behavior has changed lately.

@butonic @kobergj

[micbar]

Good starting point:

• Start to find out why the ocdav service is not passing the trace / request down to the storage provider

[butonic]

IMO we should log the requestID in the proxy only. tying logs together should be done by always enableing tracing so the traceid is not a zeroes by default. we could use a noop trace logger, but tracing itself should always be enabled to be able to aggregate logs.

obviously, passing the trace needs to work and might be affected by the same underlying bug of a context being disconnected