generate ChaosEngine from a deployment under chaos

Requirement:

• The users workflow to trigger/abort chaos should be as simple as annotating and de-annotating his application deployment.
• In other words, ChaosEngine resources should be created (triggering the experiment) and removed (aborting the experiment) upon adding an experiment specific annotation. For example: litmuschaos.io/pod-delete: true | false (or removal).
• This can be extended to handle repeated/scheduled execution, say litmuschaos.io/pod-delete-schedule: <time units> which might create a schedule custom resource (the scheduler controller then creating the engine)

Considerations:

• The chaosengine spec is today holds (a) app info / (b) experiment info / (c) run-properties. Out of these (c) and to an extent (b) are static information as far as a user/SRE is concerned and can be derived from templates the user can pull. The app info (a) is desired to be pulled by the controller under discussion: as part of generating the chaosengine attachment.

• Schedule are subject to halt/resumption. Lets say that is handled by other controllers (scheduler, as discussed above). In such cases the current engine/schedule generator should be aware and reconcile accordingly.