[wasm][debugger] Run debugger test in codespace

[ilonatommy]

Enables running debugger tests with no additional package installations.
Running a sample debugger test:

dotnet test /p:RuntimeConfiguration=Release /p:Configuration=Debug src/mono/wasm/debugger/DebuggerTestSuite --filter DebuggerTests.SteppingTests.InspectLocalsDuringSteppingIn

Changes in this PR:

• Added chromium installation to the dockerfile.
• Added --no-sandbox to arguments passed to harness when we detect that code is running in a container.

Recommendation:
use at least 8 core VM. For smaller sizes you can encounter an error: Less than 64MB of free space in temporary directory for shared memory files.

Test that always fail in codespace on main (different than typically):

DebuggerTests.ArrayTests.InvalidArrayId [FAIL]
DebuggerTests.EvaluateOnCallFrameTests.EvaluateSimpleMethodCallsError [FAIL]

Possible workaround if --no-sanbox was in some point inconvenient -> adding to devcontainer.json:

"runArgs": ["--security-opt","seccomp=.devcontainer/chrome.json"],

in this solution bigger VM is also needed because of threads' crashes:

Gathering state for process 13427 dotnet
Crashing thread 000052dd signal 00000006

unless we use the VM with 16 core or 8 core.

[ghost]

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

Issue Details

---

• Added chromium installation to the dockerfile.
• Added --no-sandbox option needed for running tests in codespaces (locally works with this option).

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

[fanyang-mono]

The change to the Dockerfile looks good to me. I wonder if you change to the test harness startup file triggered the failures on CI.

[radical]

Some of these failures were due to missing helix queues, which is fixed on main.

[lewing]

Should we print out a diagnostic message saying we've disabled sandboxes?

[eerhardt]

This approach looks good to me.

Need to remove the installation part

[thaystg]

12084e4 remove the installation part as @radical has already implemented it in this other PR