deno task should support caching based on input/output

[shinebayar-g]

I really like that I'm able to remove more and more dependencies using Deno!

v2.1 release is awesome. Perhaps this is already discussed internally, but I couldn't find any tickets here. So here we go.

With the help of task inputs and outputs it will be possible to cache task results. NX and Turbo repo uses similar model to achieve task caching.

High level API looks like this:

1. User defines task inputs and outputs
2. Deno hashes task inputs and outputs
3. Deno saves outputs in internal cache

Next time task is run:

1. Deno hashes input files again
2. Deno compares new input hash with the previous input hash.
   3a. If the input hashes don't match, Deno clears previous cached content (output) and runs task again.
   3b. If the input hashes match, deno hashes output files and compares with the previous output hash. If the output hashes don't match, restore output contents from the previous output hash. If the output hashes match, do nothing.

[dsherret]

There's a feature request here, but it's a bit broad. It might be good to break it up into issues like this one: #26462

[bartlomieju]

denoland/deno_config#142 will be required first. @marvinhagemeister mentioned he wants to work on that.