[Feature] Support a non-randomized execution order

[flakey-bit]

While randomizing the execution order is probably the right thing to do for "most" cases, there are at least some cases whereby it's not desirable.

We wanted to use this library for a "dry-run" - we needed to perform the "experiment" flow before performing the "control" flow (executing the control flow first would invalidate the results of the experiement flow, but not vice-versa).

Describe the solution you'd like
It would be useful to have an option that disables randomiziation (control/experiment) and instead executes the trials in specified order

• Experiement first, then control
• Control first, then experiment

Describe alternatives you've considered
No alternatives exist that we can think of (outside of not using the library)

[JoshHiles]

I'm thinking a new method experiment.EnsureControlRunsFirst()
It wouldn't stop the randomisation rather it would run the control first and then execute the candidates in a randomised order

[flakey-bit]

Saw this got fixed - thanks very much!! 💚

[JoshHiles]

Saw this got fixed - thanks very much!! 💚

I'm planning on getting #165 done and then I'll get a release out when the both included!