feat: deno task dependencies should allow passing additional arguments

[BlackAsLight]

A few versions ago we were allowed to change our tasks in deno.json from just a string of concatenated commands to an object that lists dependencies to be ran before the command. At the moment though these dependant tasks can only be executed as is. It would be nice if we could pass additional flags to it while still keeping that parallelism this change enabled.

Example

In this below example, deno task cov shows what I'm asking. Where both coverage and clean flags are passed to it. Allowing them to only be generated if viewing the coverage is desired.

{
  "tasks": {
    "cov": {
      "command": "deno coverage --html .coverage/",
      "dependencies": ["test --coverage='.coverage/' --clean"]
    },
    "cov:mac": {
      "command": "open .coverage/html/index.html",
      "dependencies": ["cov"]
    },
    "cov:lin": {
      "command": "xdg-open .coverage/html/index.html",
      "dependencies": ["cov"]
    },
    "cov:win": {
      "command": "start .coverage/html/index.html",
      "dependencies": ["cov"]
    },
    "test": "deno test -R='.output/' -W='.output/' --parallel --trace-leaks --reporter=dot",
    "lint": "deno lint",
    "fmt": "deno fmt",
    "ok": { "command": "deno task test --doc", "dependencies": ["fmt", "lint"] }
  }
}

[bartlomieju]

Started on this. The argument-forwarding part isn't implemented yet —
dependencies are still resolved as bare task names — so this should stay
open.

As groundwork I've put up denoland/deno_task_shell#183, which adds a
parse_task_dependency helper that splits a dependency entry like
test --coverage='.coverage/' --clean into a task name plus the literal
args to forward, reusing the existing shell parser so quotes are handled
correctly (--flag='a b' → --flag=a b). It rejects anything ambiguous
at config-load time (pipes, &&/||/;, redirects, subshells, env
assignments, and args needing runtime expansion like $VAR/~/{a,b}).

The remaining work is on the deno side:

• deserialize each dependencies entry into { name, args }
• store the args on the resolved dependency (today it's just a task id)
• append them when running the dependency, the same way root argv is
  forwarded to the root task
• key the dependency graph on (name, args) rather than task id, so the
  same task can run with different argument sets while identical ones
  still dedup

Happy to take that follow-up too if it's wanted.