Proposed changes

Ensure tedge-mapper-c8y doesn't handle incoming custom operations if received multiple times from Cumulocity.

The specific case this fixes is for custom operations from Cumulocity JSON fragements (e.g. on c8y/devicecontrol/notifications) where these execute using a command from the mapper. Since these don't use a workflow to execute, these operations didn't generate any te/... messages, so we didn't track them in active_commands. This PR changes this so that any operation with an ID is included in active_commands, and it will be removed after a 12 hour timeout elapses.

This won't fix any cases where we are using smartrest to receive the operation payload, since those messages do not have an ID included in the payload.

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

• flaky system test: Custom Operation Command.Run shell custom operation for main device and publish the status #3399

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