Allow tasks to be ran in interpreted mode

Nobody has claimed this yet.

It would be cool if we could tell the tasks to run in interpreted mode instead of waiting to compile. For larger apps, compile time on these tasks can get to be a bit much. (i.e. 90+ seconds before execution starts).

As of this writing, the [Crystal interpreter](https://crystal-lang.org/2021/12/29/crystal-i/) is still in development and requires building a custom Crystal binary with it enabled. Until it's native, this won't be available as a default option, but we could potentially make it also behind a flag.

I have no clue how the performance would be, but I'm hoping that there may be cases where running slower code in the interpreter would be the optimal choice because maybe the code won't take long to run anyway, and time to first execution would be a lot faster than waiting on the compiler.

The issue names no files, tests, or execution entry points. Start by locating how tasks are launched and how the CLI could select a custom Crystal interpreter binary behind a flag; done would require a defined interface, supported interpreter path, and evidence that task startup avoids compilation.

Written by the indexing model from the issue text.