feat: task propagation run logging

Description

feat: task propagation run logging

• added run_id property to Task object
• this id identifies a specific propagation of that task
• this is purely used for logging (in engine and services as well)
• updated relevant logs to include run id
• added the run id property to the TaskResult object as well

BREAKING CHANGE: db update

How to test

Deploy on devel, try service propagation and check all the necessary logs files, make sure nothing fails

Author's checklist

• I have followed the contribution guidelines
• This MR has been tested or does not change functionality
• I have added relevant merge request dependencies (if this MR has any)
• I have added the correct labels
• I have assigned reviewers (if any are relevant)
• I have edited the documentation (if the changes require it) or I have noted the need for the change if I do not have access to the documentation
• I have marked all introduced BREAKING CHANGES or necessary DEPLOYMENT NOTES in the commit message(s)

Reviewer's checklist

• This MR has been tested or does not change functionality
• This MR has correct commit message format

Other information

Make sure the review is thorough, not sure whether the changes to objects can break some message relaying or something of that sort

Related issues

TODO: Add relevant issue numbers in the following format (will be added automatically if the MR branch follows our branch naming conventions):

• closes STR-XXX, closes STR-YYY for issues fully resolved by this MR, or
• re STR-XXX, STR-YYY for issues only partially resolved by this MR

Closes STR-1084