docs: add --wait-for-lock flag to docs

[Wheest]

Documents iterative/dvc#10784 as an available feature.

[skshetry]

@Wheest, was this CLI option useful/helpful for your usecase as stated in iterative/dvc#10752?

[Wheest]

Yes, it's now used in all of our Bazel rules that use DVC (since they're running multiple rules in parrallel).

There's still some work we're doing with Bazel+DVC (see this stackoverflow question), but it would be interesting to upstream those if possible, not sure if there's been any discussion on that front here.

[skshetry]

There's still some work we're doing with Bazel+DVC (see this stackoverflow question), but it would be interesting to upstream those if possible, not sure if there's been any discussion on that front here.

I don't quite understand the request here for dvc as most of it looks related to bazel which i am not familiar with. Please feel free to create an issue if you have something specific in mind.

Unrelated to this, but have you tried using dvc get instead of dvc pull? It maybe be slower, but does not run into locking issues. It is useful for downloading dvc-tracked data into a directory (could be a temporary/ephemeral directory), may be useful in build systems.