Expected Behavior

Tasks are run in parallel by default when the configuration cache is enabled even when there's a cache miss.

This would also make all problems, the ones occurring when storing and the ones occurring when loading, surface on the first build. This would make things less confusing and limit the possibility to create problematic configuration cache entries.

Current Behavior

Only builds with configuration cache hits run tasks in parallel.
Builds storing the configuration cache runs as regular builds, not isolating tasks and not running them all in parallel.