Follow-up: Extract useful changes from the reverted #2482 PR

[rina23q]

Proposed changes

The reverted PR #2482 contains the changes which should not have to be reverted. This PR is the collection of such commits.

Two commits are cherry-picked from #2482 and changed the hash (important to have different hash to merge them again).

• (original commit) => (new commit in this branch)
• 31e07a8 => 566124f
• e7fc294 => d4d9568

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

[didier-wenzek]

This exactly re-introduces the reverted commits, but one slight fix might be better.

[codecov]

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (9ff6d57) 75.8% compared to head (a17f15c) 76.0%.
Report is 6 commits behind head on main.

Additional details and impacted files

Files	Coverage Δ
...es/core/tedge/src/cli/connect/bridge_config_c8y.rs	88.7% <100.0%> (+0.1%)	⬆️
...nsions/c8y_mapper_ext/src/compatibility_adapter.rs	0.0% <0.0%> (ø)

... and 9 files with indirect coverage changes

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
378	0	3	378	100	1h17m49.047s