[T.1.3] Remote Benchmarking and Machine Priming

[smarr]

In some scenarios, one would want to run benchmarks not one the local machine, but perhaps some extension device, or a remote devices that is not able to run ReBench. Examples could be some embedded devices, FPGAs, clusters with their own schedulers, or other constrained environments.

One the one hand, we need a way to allow people to configure how to do the execution and data handling, which may not be synchronous as it is assumed to be now. On the other hand, we need to adapt provenance tracking to capture details on how and where binaries were compiled, as well as about the machine executing them.

The second part of this project is to add support for priming of a machine.
Systems often manage resources based on heuristics and one may need to run a specific workload triggering these heuristics and enabling the desired machine state. This is sometimes need for instance for getting GPUs into the highest performance state.

Similar to #176, this would benefit from a validation step to verify that the desired state is reached.