Fix inconsistent cwd of run and debug command in client

[roife]

Fix #17012. Also related to #13022 and #15993.

When the kind of runnable is bin, Cargo would use the workspace root as the cwd for the run command; otherwise, Cargo defaults to the package root as the cwd for run.

Initially, r-a assumed the workspace root as the cwd for all runnables in debug command, which led to issue #13022. In this case, during unit testing, the run command would use the package root while debug would use the workspace root, causing inconsistency.

PR #15993 addressed this problem by using the package root as the cwd for debug command. However, it also resulted in an inconsistency: when executing the run command within the main fn of a package (whose target is bin), Cargo would use the workspace root, whereas debug would use the package root, leading to issue #17012.

The preferable approach is to determine the cwd based on the runnable's type. To resolve this, this PR introduces a new cwd field within CargoRunnable, allowing r-a to decide the appropriate cwd depending on the specific kind of the runnable.

[Veykril]

Sounds reasonable to me, cc @davidbarsky since you've been dabbling around this area wrt to rust-project.json, probably not too relevant but given #16840 is in a similar-ish vein

[bors]

☔ The latest upstream changes (presumably #17287) made this pull request unmergeable. Please resolve the merge conflicts.

[davidbarsky]

yeah, this seems reasonable to me, I think.

[Veykril]

@bors r+

[bors]

📌 Commit a8031e3 has been approved by Veykril

It is now in the queue for this repository.

[bors]

⌛ Testing commit a8031e3 with merge a55e8bf...

[bors]

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