Device profile twin update after successful operation

[albinsuresh]

Proposed changes

Update the device profile twin info with the last applied profile information after a successful command execution.

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

Attention: Patch coverage is 0% with 88 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
.../tedge_agent/src/device_profile_manager/builder.rs	0.00%	46 Missing ⚠️
...re/tedge_agent/src/device_profile_manager/actor.rs	0.00%	41 Missing ⚠️
crates/core/tedge_api/src/device_profile.rs	0.00%	1 Missing ⚠️

Additional details and impacted files

📢 Thoughts on this report? Let us know!

[albinsuresh]

Replaced by #3114