Fire an error event for parse errors when constructing SharedWorker

This aligns the behavior of parse errors in a SharedWorker with fetch
failures. See discussion in #5323, which has gone beyond that to also
discuss other types of errors, but for now we have agreement on parse
errors at least.

source

@@ -101577,13 +101577,17 @@ interface <dfn>SharedWorkerGlobalScope</dfn> : <span>WorkerGlobalScope</span> {
      fetch</span> steps with <var>response</var>.</p></li>
     </ol>
 
-    <p>If the algorithm asynchronously completes with null, then:</p>
+    <p>If the algorithm asynchronously completes with null or with a <var>script</var> whose <span
+    data-x="concept-script-error-to-rethrow">error to rethrow</span> is non-null, then:</p>
+
     <ol>
-    <li><p><span>Queue a task</span> to <span data-x="concept-event-fire">fire an event</span> named
-    <code data-x="event-error">error</code> at <var>worker</var>.</p></li>
-    <li><p>Run the <span data-x="environment discarding steps">environment discarding steps</span>
-    for <var>inside settings</var>.</p></li>
-    <li><p>Return.</p></li>
+     <li><p><span>Queue a task</span> to <span data-x="concept-event-fire">fire an event</span>
+      named <code data-x="event-error">error</code> at <var>worker</var>.</p></li>
+
+     <li><p>Run the <span data-x="environment discarding steps">environment discarding steps</span>
+     for <var>inside settings</var>.</p></li>
+
+     <li><p>Return.</p></li>
     </ol>
 
     <p>Otherwise, continue the rest of these steps after the algorithm's asynchronous completion,