Feature Request: Log environmentGlob hash to console w/ running lage task (Dry run)

[BrunoRDS]

Overview

In order to build automation and for all around convenience, it would be great to have a CLI command to have lage calculate and output the environmentGlob hash without needing to run a lage task w/ --logLevel=verbose.

Example: yarn lage cache --envGlobHash

Details

It would be helpful to check the environmentGlob hash without needing to trigger work not needing to be done. The specific use case I have in mind is calculating the environmentGlob hash on different platforms/environments off the same commit in a CI pipeline to gate commits verifying that the cache they produced can be used across these different platforms/environments.

Another way to consider this would be a having a --dryrun CLI option that does all the prep work for a lage task run without actually running the task. So yarn lage build --verbose --dryrun should log the environmentGlob hash to console without actually building anything.

[chazmuzz]

More generally, Lage seems to be bad at telling you which changed files are causing a cache miss. It would be great to see some improvement there