feat: add CLI + Pipeline compatibility check

[idanmuze]

This feature gives a helpful message when running the CLI to clarify whether the CLI and the slated pipeline are compatible.

I ran into an issue while working on this, however.

I failed to run any pipeline that specified a Cicada version that wasn't the same as the CLI's one.
For example, I'm running the latest CLI version, 0.1.50.

If I change the Cicada import in .cicada/test.ts from

import { Job, Pipeline } from "https://deno.land/x/cicada/mod.ts"; (which will resolve to the latest version, 0.1.50)

to

import { Job, Pipeline } from "https://deno.land/x/[email protected]/mod.ts";

I get the following error:

Error: Module does not export a Pipeline or Image
[error] Failed to run deno script

It is serialize.ts that is throwing the error.:

This is confusing. test.ts still exports the default type pipeline (the only line I changed in the pipeline is the Cicada import).

Though I'm not sure what the cause is, it likely is just the method Cicada currently uses to cache the module. It may be that different Cicada versions of Pipeline are being treated as entirely different types. This causes them not to make it passed serialize.ts.

I didn't want to make non-trivial changes to the caching code before getting feedback on whether I'm on the right track, so here is a draft.

[grant0417]

Sorry for the delay on the review here, it all looks good to me, the only change would be not actually grabbing the latest version and just say something like "using latest version of definitions"