Missing tasks in parallel steps in Presentation API

[dontcallmedom-bot]

While crawling Presentation API, 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 PresentationRequest/start() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The PresentationRequest/reconnect() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The PresentationRequest/getAvailability() algorithm resolves/rejects a promise directly in a step that runs in parallel
• The monitoring incoming presentation connections algorithm 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.}