Try to fix more of the build script to handle paths with spaces

[jwosty]

Description

Follow up to #18136

Building works when working with this repo under a path with spaces, but running tests blows up.

Tried to fix it with more quoting (with the contents of this PR), but it seems that Exec-Process in eng/common/tools.ps1 is somehow not handling spaces correctly either. And I guess that file has to be fixed via dotnet/arcade; should I file an issue there?

I'll probably just work out of a directory without spaces at this point 😅

[github-actions]

✅ No release notes required

[vzarytovskii]

Thanks, and yes, anything under eng/common should go to arcade.

[psfinaki]

Hey @jwosty, sorry for the whole experience. Naive question (I'm very bad at PowerShell), won't single quotes somehow help here?

I think at least for basic things, they have similar effect as the double ones and that sometimes helps with escaping.

[jwosty]

@psfinaki I'm no powershell guru either... I may or may not have given a snippet to chat gpt and asked it how to escape the variables for spaces, lol

I don't know. I'm just going to raise the issue in dotnet/arcade since if the problem is really rooted in there it feels silly (to me at least) to try to work around it from here.