refactor: Merge log_manager crate under tedge_log_manager

[didier-wenzek]

Proposed changes

The log_manager crate being only used by tedge_log_manager, it's better to make this clear and merge these two crates.

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Additional details and impacted files

📢 Thoughts on this report? Let us know!

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
526	0	2	526	100	1h36m51.680663s

[Ruadhri17]

Looks good but crates in cargo.toml must be sorted to please taplo.

[Ruadhri17]

Approved.

[rina23q]

Thanks for detecting this. The log_manager crate was used when we had supports both for the legacy c8y_log_plugin and the new tedge_log_manager. Since c8y_log_plugin is deprecated long time ago, the common crate log_manager no longer makes sense.