Process manager integration tests

[PawelPlesniak]

Description

Fixes # (issue_number)

Writes a minimal example of what to execute when running the SSH PM. This will be expanded heavily

Type of change

• Documentation (non-breaking change that adds or improves the documentation)
• New feature (non-breaking change which adds functionality)
• Optimization (non-breaking, back-end change that speeds up the code)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (whatever its nature)

Key checklist

• All tests pass (eg. python -m pytest)
• Pre-commit hooks run successfully (eg. pre-commit run --all-files)

Further checks

• Code is commented, particularly in hard-to-understand areas
• Tests added or an issue has been opened to tackle that in the future.
  (Indicate issue here: # (issue))

[PawelPlesniak]

Markled as ready for review to see which PRs are being actively worked on for now. Please ignore that update

[emmuhamm]

Latest changes are up, I think they are janky but thats the downside of using logs. With more time, I can get it better but for now they work in most circumstances. I would advice against putting this in any default integtests though, at least until monday when I reverify everything.

It also depends on Kurt's branch, kbiery/temp_branch_drunc_output_capture, on integtests

TODO for monday

• go through again to make sure everything works
• Update readme
• Go through personal notes to see if I forgotten anythign