Bump pdfjs-dist from 5.6.205 to 5.7.284

[ggtlvkma356]

Supersede #632

• Add polyfill for Math.sumPrecise
• Tested with Add instrumented tests and js tests #627

[inthewaves]

Our index.js passes isEvalSupported to getDocument:

globalThis.loadDocument = function () {
    const pdfPassword = channel.getPassword();
    const loadingTask = getDocument({
        url: "https://localhost/placeholder.pdf",
        cMapUrl: "https://localhost/viewer/cmaps/",
        cMapPacked: true,
        password: pdfPassword,
        iccUrl: "https://localhost/viewer/iccs/",
        isEvalSupported: false,

However, pdf.js removes isEvalSupported in mozilla/pdf.js@f6bac01 (not an error because of JavaScript permissiveness... thanks JavaScript!). It seems like a legacy option to me, but we should make sure that having it removed is fine

[ggtlvkma356]

isEvalSupported was disabled to prevent pdf.js from compiling PostScript code inside a pdf. The corresponding switch in the new version is useWasm. I have updated the PR to reflect the change.

[inthewaves]

We'd need to check if useWasm false conflicts with existing wasm usage, e.g. 99736fc

[ggtlvkma356]

Wasm is currently disabled by CSP, see #634

[inthewaves]

useWasm appears to default to true in pdf.js, but it's good that we're specifying useWasm explicitly due to the isEvalSupported change in 5.7.284.

We can manage CSP for workers in another issue/PR; it's a preexisting issue