feat: telemetry data export via a secure channel

[etorreborre]

This PR allows telemetry data (logs and spans) to be exported via a secure channel to the authority node.
This is the first step for exporting telemetry data via a secure channel, the next step will be to export it via the project node.

gRPC data interception

When a project is ready, the log and span exporters are set with a gRPC client which packs the gRPC requests into Ockam messages.

Those messages are sent to a HttpForwarder worker which deserializes the requests and forwards them to an Opentelemetry collector endpoint.

Documentation

I started a telemetry.md document to describe the different options which can be used to export telemetry data.

TcpTransport

The creation of a TcpTransport with the TcpTransport::create(ctx: &Context) method now checks if the transport has not already been created. If it has been created, it returns the same TcpTransport instead of returning a new one which would have a new internal registry and potentially lose some data.

This avoids the passing of both the Context and a TcpTransport when creating the SecureClient that will be used to send telemetry data.

Dependencies upgrades

This PR also upgrades the opentelemetry crates since there were recent breaking changes and more are coming up.