chore(rebuild): Clarify what to do with non-ASCII characters (#486)Th…

…e algorithm for parsing Content Security Policies was accepting a serialized CSP (list), i.e. a string matching the CSP grammar, but it was being called with a string or a byte sequence as argument. The spec was not saying anything about what to do when parsing policies containing non-ASCII characters.This change clarifies that along the lines of the discussion on #473.

SHA: 49ae457
Reason: push, by @antosart

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>