Ensure tasks are resolved when run from extension host

[alexr00]

Fixes #101884

[alexr00]

This issue was caused by 1abf21d.
1abf21d fixed some timing issues with running tasks from the extension host by making an extra trip from the extension host to main to get the task execution, essentially splitting mainThreadTasks $executeTask into $getTaskExecution (called first) and $executeTask (called second).

This split is what caused #101884. When a task execution is made, the task is effectively resolved. So, in the old way with just $executeTask, the task was resolved and then immediately run. Now, the task is resolved, passed to the extension host where it loses some important stuff (like the depends on info), passed back to the main thread, then executed. There needs to be another resolve in there before it is run, so that it can pick up the missing depends on info again.

In short, I have changed the one place where a TaskHandleDTO is passed into $executeTask to pass that again, and I have changed $executeTask back to it's pre-timing fix behavior. This still preserves the timing fixes, since $getTaskExecution is still being called first. The changes to $executeTask that caused this issue were not to fix the timing problems, but instead to increase performance by not resolving the task again. $executeTask and $getTaskExecution should look very similar, with $executeTask performing the additional run.