investigate if proof cache should store more state

[lsf37]

Currently, aws-proofs always rebuilds the following:

• scala component
• standalone C parser
• haskell kernel

This is because the cache doesn't store build outputs for these. Investigate what would be necessary to include them.

It might be fine to just scan and add them to a second tar file. Potential problems when directory structure changes and the cache then pollutes the source tree with random stuff. Then again, it should reset automatically after the regular clean build, so problems will be limited in time.

[lsf37]

A problem where that would have hit was the recent update to GHC 9/cabal v2 structure. The new cabal commands fail in a context produced by the old cabal. Then again, this is fairly rare.

Otherwise, the only thing needed to include more things in the cache is a list of paths to include.