Provide nested manifests and manifests covering edge-case scenarios for phased execution

[zanete]

Why: Sub of #762

What: Support the development of #809 with nested manifests and other manifests covering edge case scenarios

Scope of work:

• manifests/examples/pipelines/nesting.yml
• manifests/examples/pipelines/pipeline-with-mocks.yml

[zanete]

cc @jmcook1186 FYI here is the issue about manifests specific to phased execution development

[jmcook1186]

Issue is that every manifest in our examples folder is supposed to have at least one corresponding file in the ouputs folder - a success case and ideally at least one negative/failure case.

[zanete]

As discussed in the standup, After @narekhovhannisyan changes the old manifests will be broken and not usable for the phased execution, so we will have to rework all of the examples and outputs. There is an issue #812 to handle this.
The scope of this issue is to provide the minimal set of manifests for @narekhovhannisyan to continue development, for example:

• manifests/examples/pipelines/nesting.yml
• manifests/examples/pipelines/pipeline-with-mocks.yml

[zanete]

@MariamKhalatova please confirm you are able to help with this and the requirement is clear? if not, please consult @narekhovhannisyan

[MariamKhalatova]

@zanete I have updated these manifests locally, however I'm blocked by @narekhovhannisyan since he hasn't pushed his changes yet. Waiting for him to publish the branch.

[zanete]

there's currently an issue with dependency on time sync which needs to be resolved in order to merge it, @manushak and @narekhovhannisyan to have a sync about this