Proposed changes

If tedge-failed, process error code and stderr were printed 2 times like this:

failed to deploy configuration file: process '/usr/bin/sudo' returned non-zero exit code (1); stderr="sudo: a password is required": process '/usr/bin/sudo' returned non-zero exit code (1); stderr="sudo: a password is required"

Now it doesn't contain a duplicate:

failed to deploy configuration file: process '/usr/bin/sudo' returned non-zero exit code (1); stderr="sudo: a password is required"

This was due to unnoticed wrapping of the error types: all the functions returned ConfigManagementError, but we still wanted to attach context, so we had the following nesting, which screwed up anyhow's error causes formatting:

ConfigManagementError::Other(anyhow::Error(source: ConfigManagementError::Other(anyhow::Error)))

Immediate function error type was changed to anyhow::Error, so now we only have a single conversion to ConfigManagementError on the outermost function.

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

Question to @reubenmiller: how to tag these small PRs that are fixes, but minor ones, for which no issue was reported? I could tag this as an improvement, but it would probably be a bit misleading since the previous behaviour really was unintended, so for release notes perhaps it should categorised as a fix?