[wasm] Fix AOT publish in paths with space on Windows

[ilonatommy]

Connected to investigation: #92399.

This is only fix for Windows, so we could not change the TmpPath for other platforms yet.

1. When WasmDedup=true we had error : Can not open image C:\repos\wbt because the path C:\repos\wbt artifacts was not put into quotations. This was a problem for all platforms and is fixed everywhere.
2. _AOTObjectFile items should not only be separated by space but also put into quotations, otherwise a spaced path will be treated as 2 separate items.
3. Tests that are using the path to the wbt test project were edited.

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Connected to investigation: #92399.

This is only fix for Windows, so we could not change the TmpPath for other platforms yet.

1. When WasmDedup=true we had error : Can not open image C:\repos\wbt because the path C:\repos\wbt artifacts was not put into quotations. This was a problem for all platforms and is fixed everywhere.
2. _AOTObjectFile items should not only be separated by space but also put into quotations, otherwise a spaced path will be treated as 2 separate items.

Author:	ilonatommy
Assignees:	ilonatommy
Labels:	arch-wasm, area-Build-mono
Milestone:	-

[maraf]

Looks good to me 👍

[radical]

nit:

Suggested change

	processArgs.Add('"' + aItem.ItemSpec + '"');
	processArgs.Add($"'{aItem.ItemSpec}'");

[radical]

What is the remaining issue on linux/macos?

[ilonatommy]

What is the remaining issue on linux/macos?

That while a sample repro for them work, when the fix is applied to the repo, it fails. Please, see #92399 (comment) and the investigation PR for reference.

Shortly: in Linux you can escape space either by putting the string into quotation OR by using backslash. If we try on a sample .c file both methods work. However, applying it in the code, that produces .rsp file as expected + command as expected, the command fails.

[radical]

What is the remaining issue on linux/macos?

That while a sample repro for them work, when the fix is applied to the repo, it fails. Please, see #92399 (comment) and the investigation PR for reference.

Shortly: in Linux you can escape space either by putting the string into quotation OR by using backslash. If we try on a sample .c file both methods work. However, applying it in the code, that produces .rsp file as expected + command as expected, the command fails.

Can you please add this to the issue tracking the linux case of this problem?

[ilonatommy]

/backport to release/8.0-staging

[github-actions]

Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/8702511263