fix: reflect changes to variables in otel-config file
What
This change makes the otel config file secret be non-secret by not storing any sensitive information in the file.
Instead of retrieving the password directly from Vault and embedding it in configuration file, the code now stores the password as an environment variable that gets loaded at runtime.
This approach means that we don't have to use secret_data_wo and secret_data_wo_version anymore as these parameters rely on secret_data_wo_version changing to trigger an update (see issue in the "Why" for a detailed explanation).
Why
Edited by Gonzalo Servat