How to reproduce:
1. Open the "burst_build_failure" project
2. Build the project for the Windows platform

Expected result: project successfully builds
Actual result: building process is interrupted by Burst errors

Reproduced: 1.6.6 (2021.3.22f1), 1.7.2 (2021.3.22f1), 1.8.0 (2021.3.22f1), 1.8.3 (2021.3.22f1)
Could not test with: 2020.3.46f1 (could not resolve scripting errors)
Fixed in: 1.8.4 (2021.3.22f1, 2022.2.13f1, 2023.1.0b10, 2023.2.0a8)

Reproduced on: Windows 10 (by reporter), Windows 11
Could not test on: macOS Ventura 13.0 (M1), Ubuntu 20.04 (could not resolve scripting errors)

Build failure log #1:

{noformat}Library\Bee\artifacts\WinPlayerBuildProgram\AsyncPluginsFromLinker: Failed to find entry-points:
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&){noformat}

Build failure log #2:

{noformat}Building Library\Bee\artifacts\WinPlayerBuildProgram\AsyncPluginsFromLinker failed with output:
UnityEditor.Build.BuildFailedException: Burst compiler (1.8.3) failed running{noformat}

Build failure log #3:

{noformat}Build completed with a result of 'Failed' in 149 seconds (148652 ms)
2 errors
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&){noformat}

Notes:
1. WebGL builds indefinitely - one build took over 1 hour and it still did not finish building
2. The WebGL building process hangs on “Linking build.js (wasm)”
3. When the building process is canceled, a zombie process lingers - “wasm-ld.exe”. This process ends up hogging more and more memory over time