refactor(config): add independent toggles for enabling traces and metrics

[SanchithHegde]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

This PR adds two configuration variables for toggling traces and metrics independently instead of using a single toggle to enable both. In addition, this PR introduces one more configuration variable to ignore errors during traces and metrics setup, if required.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

The log.telemetry.enabled configuration variable is no longer being used, the log.telemetry.traces_enabled and log.telemetry.metrics_enabled configuration variables must be used instead for toggling traces and metrics, respectively. In addition, errors during traces or metrics setup can be ignored using the log.telemetry.ignore_errors configuration variable.

Motivation and Context

This would allow us to have metrics and traces independently enabled, as required.

How did you test it?

Manually.

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable

[lsampras]

I wonder if we should update the config structure here as well...

currently we have

I think the below could be a better representation...

[SanchithHegde]

I wonder if we should update the config structure here as well...

currently we have

I think the below could be a better representation...

I'd prefer to take this up in a separate PR.