Proposed changes

• Re-enable some maximum message count assertions that were skipped while fix: fallback to systemctl command when debian helpers are not available #3402 was awaiting a fix
• Remove the maximum message count assertion in the custom smartrest operation test. In the case of custom smartrest operations, the mapper makes no attempt to de-duplicate incoming operations, so we can't guarantee that an operation won't be executed twice, particularly in the case of system tests which run just after tedge has started up.

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. You can activate automatic signing by running just prepare-dev once)
• I ran just format as mentioned in CODING_GUIDELINES
• I used just check 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