Description

This is the first one of a few PR that address the State Management in SK Processes. Dividing in smaller PRs since feature contain multiple big components.

In this PR

• SAVE: After running a Process, adding capability to extract process state for stateful processes - works also with nested processes
• LOAD: from a Process State data structure, loading state to ProcessBuilder before Build() to apply it to Process and use it on runtime. For now only focusing on Step State only, not focusing on exact replica of processes (using same ids)
• Samples: Adding more samples in Step02_FoodPrep that load existing State from file and use it to run specific food pre processes, also samples on how to save the state

Out of Scope but coming up in future PRs

• How to deal with processes running that have the same id (processid, stepid)
• In the future, ProcessStep State will have versions, so if loading an old state to a process with a new state version there is:
  • validation
  • migration strategy placeholder to add custom state migration
• A new way to create ProcessBuilders so that on save, processTypeIds can be interpreted instead of needing to pass all steps, and edges when loading a ProcessBuilder from file - current DAPR implementation
• More samples showcasing more complex scenarios

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄