`deno task --recursive <task>` should execute packages based on inter-dependencies

Say given two packages named `a` and `b` in a workspace... if `a` depends on `b`, then the task execution order should be `b`, `a` rather than `a`, `b`.

This is important because the task in `a` might depend on `b` being built (ex. needing to build `b` before `a`).

Version: Deno 2.3.3
