feat: Config and log management workflows

[didier-wenzek]

Proposed changes

Update the log and config operations so those can be used by the workflow system,
enabling the ability to trigger a log or config update as a sub operation.

• Make log and config message types similar to those used for the workflows
• Dynamically register Restart operation
• Dynamically register Software operations
• Make the LogManagerActor acting on LogUploadCmd instead of MqttMessage
• Make the ConfigManagerActor acting on ConfigSnapshotCmd & ConfigUpdateCmd instead of MqttMessage
• Enable log operation workflows
• Enable config operation workflows
• Add system tests checking that LogUpload can be triggered as sub operations
• Add system tests checking that LogUpload can be overridden
• Add system tests checking that ConfigSnapshot can be triggered as sub operations
• Add system tests checking that ConfigSnapshot can be overridden
• Add system tests checking that ConfigUpdate can be triggered as sub operations
• Add system tests checking that ConfigUpdate can be overridden

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

#2836

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

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
450	0	3	450	100	1h13m12.911536s

[codecov]

Codecov Report

Attention: Patch coverage is 65.20270% with 206 lines in your changes are missing coverage. Please review.

Project coverage is 78.0%. Comparing base (0b974d5) to head (15b7e26).
Report is 3 commits behind head on main.

Additional details and impacted files

Files	Coverage Δ
crates/common/mqtt_channel/src/topics.rs	86.2% <ø> (ø)
crates/core/c8y_api/src/json_c8y.rs	92.4% <ø> (ø)
crates/core/tedge_actors/src/builders.rs	96.6% <100.0%> (+19.6%)	⬆️
crates/core/tedge_actors/src/channels.rs	84.3% <ø> (+13.7%)	⬆️
crates/core/tedge_agent/src/agent.rs	0.0% <ø> (ø)
...tes/core/tedge_agent/src/software_manager/actor.rs	62.7% <100.0%> (+3.4%)	⬆️
...tedge_agent/src/tedge_operation_converter/tests.rs	94.5% <100.0%> (+0.6%)	⬆️
crates/core/tedge_api/src/lib.rs	100.0% <100.0%> (ø)
crates/core/tedge_api/src/workflow/mod.rs	60.5% <100.0%> (ø)
...s/c8y_mapper_ext/src/operations/config_snapshot.rs	90.5% <100.0%> (ø)
... and 20 more

... and 4 files with indirect coverage changes

[reubenmiller]

Approved.

Great job (especially for the sustained effort!)