internal: extend check.overrideCommand and buildScripts.overrideCommand docs

[RalfJung]

Extend check.overrideCommand and buildScripts.overrideCommand docs regarding invocation strategy and location.

However something still seems a bit odd -- the docs for invocationStrategy/invocationLocation talk about "workspaces", but the setting that controls which workspaces are considered is called linkedProjects. Is a project the same as a workspace here or is there some subtle difference?

[Veykril]

They are the same in this regard. The terms are kind of confusing, projects, workspaces, cargo workspaces, vscode workspaces. linkedProjects is named as such because it was initially meant for pointing to the rust-project.json format, but you can also point it to cargo manifests.

[RalfJung]

To make things worse, the "root" InvocationLocation is documented as

The command will be executed in the project root.

So this uses "project" in a way very different from linkedProjects...

I pushed a change which should help elsewhere, but I don't have a good idea for what to do about this one.

[Veykril]

We should probably define some terms and use them appropriately in the docs, as sometimes we do want to talk about the entire opened directory opposed to contained cargo workspace within. I can put that on my homework list

[Veykril]

Damn, now i regret the invocationlocation config option being name workspace.... project would've been more appropriate I think

[Veykril]

@bors r+

[bors]

📌 Commit ba7f2bf has been approved by Veykril

It is now in the queue for this repository.

[bors]

⌛ Testing commit ba7f2bf with merge 2b580a1...

[bors]

☀️ Test successful - checks-actions
Approved by: Veykril
Pushing 2b580a1 to master...