Fix running WebAssembly Browser App from VS

[thaystg]

As $(OutputPath) is not absolute path, we need to add $(MSBuildProjectDirectory)

Tested:

• Create a new WebAssembly Browser App on VS and run, change WasmAppDir and run again.
• Create a new WebAssembly Console App on VS and run, change WasmAppDir and run again.
• Create a new wasmbrowser app using command line and run;
• Create a new wasmconsole app using command line and run;
• Create a new wasmbrowser app using command line and dotnet build and dotnet run --no-build;
• Create a new wasmbrowser app using command line and dotnet build and dotnet run --debug;

Also, added tests for command line runs. But a few of the tests are disabled because the tests would be using 7.0 targets, but 7.0 doesn't have the fix yet.

Fix #75356

[ghost]

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

As $(OutputPath) is not absolute path, we need to add $(MSBuildProjectDirectory)

Fix #75356

Author:	thaystg
Assignees:	-
Labels:	area-Infrastructure-mono
Milestone:	-

[ghost]

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

Issue Details

---

As $(OutputPath) is not absolute path, we need to add $(MSBuildProjectDirectory)

Fix #75356

Author:	thaystg
Assignees:	thaystg
Labels:	NO-MERGE, arch-wasm, area-Build-mono
Milestone:	-

[radical]

/backport to release/7.0

[github-actions]

Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/3042387685

[radical]

The corresponding 7.0 PR has been merged. Once the packages from that are available, the disabled test here can be enabled again.

[lewing]

failure is #74302