More Accurate Task Caching

[Cugatay]

Right now, structure for task caching is like this:

{
    files: Record<string, { // here, string being the file name
        tasks: { failed: boolean, command: string }
    }>
}

Which causes uncached tasks if we change the order of tasks. A task's output usually doesn't depend on the order we run them, I know that if you changed some variables in the system or you did something tricky it'll change then, but usually it'll not. In the case where it affects you, you can say no to skipping then, there's no cost of pressing don't skip. But there's a cost when you don't skip a task you can skip.
To resolve this, we'll change the structure as below:

{
    files: Record<string, { // here, string being the file name
        tasks: Record<string, {failed: boolean}> // here, string being the command we run
    }>
}

We use { failed: boolean } instead of just boolean, because at some point I believe we might add other fields, but it's not clear yet. So we can use only a boolean at the moment.

[Cugatay]

I'm keeping this as discussion, since achieving this task will create hashmaps that we'll need to search through instead of one index in an array, therefore reducing the performance of searching cached tasks.