Server-side replays

[schustmi]

Describe changes

This PR enables replaying pipeline runs from the server.

Key differences between replays and re-runs:

• Replays allow skipping steps. Skipping a step means it will not be re-executed, even if cache was disabled for the step or if some of the inputs changed in the meantime.
• Replays allow overriding step input artifacts. Compared to re-runs, replays not only allow overriding step parameters but even override inputs that came from an upstream step in the original run.

Other required changes:

• Update materializers for JSON serializable types to work from the server. This means they cannot use fileio anymore as that depends on the filesystem registry which is disabled on the server. Instead, they now use the artifact store directly.

Pre-requisites

Please ensure you have done the following:

• I have read the CONTRIBUTING.md document.
• I have added tests to cover my changes.
• I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
• IMPORTANT: I made sure that my changes are reflected properly in the following resources:
  • ZenML Docs
  • Dashboard: Needs to be communicated to the frontend team.
  • Templates: Might need adjustments (that are not reflected in the template tests) in case of non-breaking changes and deprecations.
  • Projects: Depending on the version dependencies, different projects might get affected.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (add details above)