.github/workflows: Wasm test failures on GitHub Actions

[hajimehoshi]

Ebitengine Version

9de408a

Operating System

• Windows
• macOS
• Linux
• FreeBSD
• OpenBSD
• Android
• iOS
• Nintendo Switch
• PlayStation 5
• Xbox
• Web Browsers

Go Version (go version)

1.23.2

What steps will reproduce the problem?

Just run Wasm tests on GitHub Actions

What is the expected result?

The tests pass

What happens instead?

The tests failed to run

Run # Wasm tests don't work on macOS with the headless mode enabled, but the headless mode cannot be disabled in GitHub Actions (#2972).
?   	github.com/hajimehoshi/ebiten/v2/audio/mp3	[no test files]
?   	github.com/hajimehoshi/ebiten/v2/audio/wav	[no test files]
chrome failed to start:
[61680:61680:[10](https://github.com/hajimehoshi/ebiten/actions/runs/11346056487/job/31557179210#step:25:11)15/133729.414342:FATAL:zygote_host_impl_linux.cc(128)] No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise seehttps://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

Anything else you feel useful to add?

See https://github.com/hajimehoshi/ebiten/actions/runs/11345790594/job/31557159899