Quickchecks don't execute unless `--compare=jit`

[dank-openai]

Describe the bug
Quickchecks don't execute unless --compare=jit.

Why would I want to slow down quickcheck execution by running it twice (interpreted and jit), and using the slow interpreter? What if I trust that JIT is correct and I just want to execute my quickcheck 4 billion times, as quickly as possible?

To Reproduce

1. Make a file with a quickcheck in it, name it foo.x
2. dslx_interpreter_main-arm64 --evaluator ir-jit foo.x, observe: [ SKIPPING QUICKCHECKS ] (JIT is disabled). Also skips quickchecks: --compare=none --evaluator ir-jit
3. dslx_interpreter_main-arm64 --compare=jit foo.x, observe RUN QUICKCHECK
4. Note that if you supply both flags, that's rejected: --compare flag is only supported on --evaluator=dslx-interpreter

Expected behavior
I would expect that executing quickchecks as quickly as possible (i.e. with evaluator=jit and compare disabled) to be encouraged and accepted. I don't want to compare the interpreter against the JIT, that's just massively slowing things down.

[meheff]

#3060 will fix this issue, at least the confusing bit about not being able to run quickcheck tests when comparator is none. However, quickcheck tests are never and were never run twice when the comparator was set. Admittedly, it's a bit confusing. They only run with the jit (with the new PR, you can run it with the IR intepreter with a special flag which might be nice for debugging) and no comparison is ever done. So @dank-openai if you are running into quickcheck slowness it is not due to the quickchecks being run with the interpreter.