Use correct set of source expressions in script directives pre-request check

[bakkot]

The script directives pre-request check has a part where it talks about the hash-algorithm of an arbitrary source expression. That doesn't make sense. But there's already a variable in scope holding just the hash-source subset of source expressions, which isn't used for anything else except a non-emptiness check. Presumably it should be used instead.

For IPR I would consider this to be non-substantive.

---

Preview | Diff

[w3cbot]

sideshowbarker marked as non substantive for IPR from ash-nazg.

[sideshowbarker]

Rebased (and dropped index.html from the changeset)

[annevk]

index.html needs to be there though, otherwise the published specification does not get updated.

[sideshowbarker]

index.html needs to be there though, otherwise the published specification does not get updated.

Now that we have the GitHub Actions autodeploy stuff set up, the published specification will automatically get updated when this is merged to the main branch.

[antosart]

Thanks for fixing this!