Proposed changes

RUST_LOG can be used to more precisely control logging configuration and is undocumented and used by developers. For this reason, I think when using it we can enable line numbers to show the location of the log statement to more easily find relevant code.

Example (issue #2739):

Start tedge-mapper with RUST_LOG:

RUST_LOG=info tedge-mapper c8y

Publish a message to trigger some error log:

tedge mqtt pub -r te/device/child1///cmd/config_update ''

tedge-mapper-c8y output:

2024-10-29T09:58:14.710505474Z ERROR c8y_mapper_ext::converter: crates/extensions/c8y_mapper_ext/src/converter.rs:139: Mapping error: EOF while parsing a value at line 1 column 0

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments