Helm installation with tracing.enabled == false spams logs with tracing errors

[W3D3]

Environment

• Kubuntu 22.04.2 LTS x86_64
• Unguard v0.8.1

When installing unguard using the new helm method, when not specifying the tracing profile for skaffold (or just generally not setting the tracing.enabled helm value to true), this results in some services trying to write traces, but failing to do so due to wrong/missing config.
The observed services that spammed their logs with tracing-related error messages were:

• microblog-service
• proxy-service

To Reproduce
Run skaffold run without any arguments and observe the logs of microblog-service and proxy-service

Expected behavior
I would expect none of the services to attempt to write traces if tracing.enabled is set to false.

Screenshots
Logs of the microblog-service attempting to write traces and failing:

Logs of the proxy-service attempting to write traces and failing:

Additional context
Example from proxy-service.yaml shows that we do not set any tracing related env vars of tracing.enabled being false, which results in the default behaviour:

[MfCrizz]

With PR #55 the expected behavior is restored.
No more tracing-related error messages:

• microblog-service
  
• proxy-service