Allow using the random scheduler in benchmarks

With !61 (merged) (#87 (closed), #117 (closed), #118 (closed)), we have a random scheduler for Kubernetes. Now we need a way to tell our benchmarks that this scheduler should be used. I guess the preferred way would be creating a SchedulerPatcher such that a user could specific a configOverride, which enables the random scheduler.