[Proposal] Enable parallel streams of work for the Pipeline Automation of the Green Review for Falco

[AntonioDiTuri]

Related to #83.

Dependencies between proposals

In order to enable every contributor to test its own proposal we need to eliminate some inherent dependencies between the steps:

1. TRIGGER AND DEPLOY
2. RUN
3. REPORT

There is a simple sequential dependency 1 -> 2 -> 3

@nikimanoledaki was wondering how we can let contributors work on the streams in parallel.

One possible solution

One solution I thought about might be to have different namespaces:

In each of the namespace the dependent part can be executed once in the setup
The TRIGGER AND DEPLOY namespace would be just empty
In the RUN namespace falco would be already installed
And in the REPORT namespace falco is already installed and the use case has been already triggered.

Important question

Do you think it makes sense to do some extra work to set up a test/development environment?
What is best in this case? Shall we just focus all the efforts on solving one proposal after another?

Do you have other ideas?