docs: Drop invalid --depth=0 from clone examples (#14931)
### Description
Four pages suggest cloning with `--filter=blob:none --depth=0` so that
`--affected` and `turbo query affected` have enough history. Git doesn't
accept a depth of 0:
```
$ git clone --filter=blob:none --depth=0 <repo>
fatal: depth 0 is not a positive number
```
A blobless clone (`--filter=blob:none`) already keeps the full commit
history, so this drops `--depth=0` and leaves the rest of the advice as
it is. Pages: `constructing-ci.mdx`, `skipping-tasks.mdx`, `query.mdx`
and `run.mdx`.
### Testing Instructions
Run `git clone --filter=blob:none <repo>`, then `git rev-parse
--is-shallow-repository` in the clone. It prints `false`. With
`--depth=0` added, the clone fails with the error above.
---------
Co-authored-by: Anthony Shew <anthonyshew@gmail.com>