Integrate new tracing services to forknet setup

[tayfunelmas]

Currently @robin-near is managing a server to contain tracing services.
Related information here: https://docs.google.com/document/d/1EcpsF4ovGiBOZE4voeul6PZJPcrk7CxUudlQ3qxt37A/edit

We patch this commit to point from the validator nodes to the opentelementry trace collector in this server.

Instead of managing it in a personal server, we should have a dedicated tracing server for the forknet setup; it should be brought up together with other nodes and the nodes should point to the tracing server for OpenTelemetry traces. See a related thread here.

[andrei-near]

Adding a tracing server in https://github.com/Near-One/infra-ops/pull/77 .
To enable tracing server, set the tracing_server variable to true, i.e:

terraform apply \
    -var="chain_id=testnet" \
    -var="unique_id=tracing-test" \
    -var="start_height=1111" \
    -var="**tracing_server**=true"

Once TF finished provisioning mocknet network, the tracer IP address will be shown and can be used in when preparing neard with neard_runner:

Outputs:
tracer_public_ip = "104.197.219.173"

[tayfunelmas]

The tracing server setup is done and now it is part of the forknet setup.
What is left is passing the IP address of the tracing server to the neard nodes.
It is currently done manually by changing the local mirror.py to set the OTEL_EXPORTER_OTLP_TRACES_ENDPOINT environment variable. We need to pass it to the init-neard-runner or new-test command and propagate through the start-neard operation within mirror.py.

[tayfunelmas]

Tracing node is now part of the mocknet setup. Closing this one.