Missing tasks in parallel steps in Indexed Database API 3.0

[dontcallmedom-bot]

While crawling Indexed Database API 3.0, 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 IDBFactory/databases() 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.}

[inexorabletash]

When this is being fixed, it would be nice to update the spec with these as well:

• Define queue a database task as queue a task against the database task source
• Update all the places that just call queue a task to more explicitly queue a database task.

(The lack of referencing globals and realms also need a serious revisit, but that's even further out of scope.)