fix(#2370): use bridge topic id in service_monitor

[Bravo555]

Proposed changes

Use the correct bridge topic id when converting health status message.

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

• Health status message mapping doesn't work when topic contains bridge #2370

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 ✅

Project coverage is 76.3%. Comparing base (6c5f45c) to head (98ccfe7).
Report is 36 commits behind head on main.

Additional details and impacted files

Files	Coverage Δ
crates/core/tedge_api/src/mqtt_topics.rs	87.4% <ø> (-0.2%)	⬇️
crates/extensions/c8y_mapper_ext/src/converter.rs	83.3% <100.0%> (ø)
crates/extensions/c8y_mapper_ext/src/lib.rs	88.8% <ø> (ø)
...s/extensions/c8y_mapper_ext/src/service_monitor.rs	96.4% <100.0%> (+<0.1%)	⬆️

... and 26 files with indirect coverage changes

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
429	0	3	429	100	0s

[didier-wenzek]

With this change, the az bridge is not reported as a service on c8y. This could make sense, but is this what we expect?

[albinsuresh]

We can't assume this hardcoded device/main topic id even for the main device since we support overriding device_topic_id via the config. That being said, I'm not fully sure if all tedge components properly respect that config setting yet either. I'm fairly sure that it is still hardcoded in many places.