Create Jenkins validation experiments for our experiments

[devos50]

A particular problem of Gumby is that it sometimes contains dead experiments, e.g., experiments that are not executed/relevant anymore. Also, changes in external software (such as IPv8/Tribler) can break the experiments in Gumby. We need to know when an experiment is broken or invalid. One policy could be to require that every experiment has an associated Jenkins job. These validation experiments can then periodically run, e.g., every week at a set time.

Note that we already have a few Tribler-related validation experiments in Jenkins.

Estimated time: 1-2 weeks