ref: Integration tests

[bitsandfoxes]

Instead of having duplicate integration test scripts for each platform, now that we have them all covered, merge them into one.

#skip-changelog

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

This PR will not appear in the changelog.

---

_{🤖 This preview updates automatically when you update the PR.}

[sentry]

Bug: The Wait-Process -Timeout command will cause an unhandled exception on timeout because $ErrorActionPreference is set to "Stop", crashing the test script.
_{Severity: MEDIUM}

Suggested Fix

Wrap the Wait-Process call in a try/catch block to handle the timeout exception gracefully. Alternatively, override the error handling for this specific command by adding -ErrorAction SilentlyContinue to the Wait-Process call. This will prevent the script from crashing and allow the intended timeout logic to proceed.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: test/IntegrationTest/Integration.Tests.ps1#L52

Potential issue: The script sets `$ErrorActionPreference = "Stop"` globally. When the
`Wait-Process -Timeout` command on line 52 times out, it generates what is normally a
non-terminating error. However, due to the global error preference, this is promoted to
a terminating exception. Because this call is not wrapped in a `try/catch` block, the
script will crash. This prevents graceful timeout handling, subsequent cleanup code from
running, and leads to the test server process leaking resources on the CI runner.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Shell expansion breaks MSBuild WebGL target on Linux/macOS

Medium Severity

The UnitySmokeTestPlayerWebGL target wraps $$env:SENTRY_TEST_PLATFORM and $$env:SENTRY_TEST_APP inside a double-quoted pwsh -Command string. MSBuild's $$ escaping only protects against MSBuild property evaluation, producing a literal $ in the output. On Linux/macOS, the Exec task invokes /bin/sh, which interprets $env inside the double-quoted string as a shell variable and expands it to an empty string, mangling the PowerShell command into something like :SENTRY_TEST_PLATFORM = 'WebGL'. The old command had no $env: references and worked cross-platform.