Implement caching mechanism for StarknetCompiler and CairoCompiler

[Arcticae]

This caching mechanism should be capable of:

• Saving the compiled artifacts somewhere in a file, alongside with a hash of the compiled code
• Comparing the stored artifacts' hashes with a hash of the files to be compiled, and determining if the files need re-compilation
• Supporting storing pre-processed and compiled files in-memory in order to avoid compiling/processing the same file twice in one program run (thus making the code cleaner, so we don't have to pass the compiled/preprocessed programs around)
• Above in-memory compilation data should be accessible through the workers of test runner. This might come with a challenge to make those picklable

A performant hash function has to be chosen, and some decorators to compilation methods, that compare the parameters and check for cached values.

This task should somehow also do an assessment of performance of caching the compiled files on the FS.

Note: This is not the highest priority, should be done probably last, as it's not necessary for the new testing arch to work.

[MaksymilianDemitraszek]

It has low priority

[kasperski95]

Reference — Caching in Buck: https://youtu.be/uvNI_E0ZgZU?t=976

[kasperski95]

Scarb should be responsible for caching Cairo compilation results.

[kasperski95]

Contract name in tests should resolve to the build output. Caching would be a functionality of protostar build.

[MaksymilianDemitraszek]

Moving it to the next milestone