cli: remove special template on query subcommand

[grouville]

One of the action items discussed in #7107 (comment)

dagger query is not the main entrypoint of the dagger CLI anymore. Even though the special template made some sense, it is a code duplication to maintain. With the upcoming changes (titles in bold, etc ...) and the remaining presence of the example on the command's help, it does make sense to remove it and keep a single source of truth

New output

./dagger query --help
Send API queries to a dagger engine.

When no document file is provided, reads query from standard input.

Can optionally provide the GraphQL operation name if there are multiple
queries in the document.

Usage:
  dagger query [flags] [OPERATION]

Aliases:
  query, q

Examples:
dagger query <<EOF
{
  container {
    from(address:"hello-world") {
      withExec(args:["/hello"]) {
        stdout
      }
    }
  }
}
EOF


Flags:
      --doc string        Read query from file (defaults to reading from stdin)
  -m, --mod string        Path to dagger.json config file for the module or a directory containing that file. Either local
                          path (e.g. "/path/to/some/dir") or a github repo (e.g. "github.com/dagger/dagger/path/to/some/subdir")
      --var strings       List of query variables, in key=value format
      --var-json string   Query variables in JSON format (overrides --var)

Global Flags:
  -d, --debug             show debug logs and full verbosity
      --progress string   progress output format (auto, plain, tty) (default "auto")
  -s, --silent            disable terminal UI and progress output
  -v, --verbose count     increase verbosity (use -vv or -vvv for more)

cc @marcosnils, as he was the original author of this

[helderco]

🚢