Missing tasks in parallel steps in WebDriver

While crawling WebDriver, the following algorithms fire an event, or resolve or reject a Promise, within a step that runs in parallel without first queuing a task:

• The algorithm that starts with "The remote end steps, given session, URL variables and parameters are:" resolves/rejects a promise directly in a step that runs in parallel
• The algorithm that starts with "The remote end steps, given session, URL variables and parameters are:" resolves/rejects a promise directly in a step that runs in parallel

See Dealing with the event loop in the HTML specification for guidance on how to deal with algorithm sections that run in parallel.

_{Cc @dontcallmedom @tidoust}

_{This issue was detected and reported semi-automatically by Strudy based on data collected in webref.}

Start with the WebDriver execute-script and execute-async-script algorithms linked in the issue, then read HTML's “Dealing with the event loop” guidance. Check each remote end steps section for promise resolution or rejection inside an in-parallel step. Done means both algorithms follow the required task-queuing behavior.