Move responsibility for configuring PDF worker to the consumer

[andriivitiv]

Details

We have switched between the modern and legacy PDF worker multiple times in the past. Each time we do this, we must update both E/App and this repo. PR #45 and Expensify/App#56473 are good examples of how we had to implement the same code twice, only to remove it later (again in both repos).

Furthermore, setting pdfjs.GlobalWorkerOptions.workerSrc in E/App has no effect because it would get overridden by this line:

react-fast-pdf/src/PDFPreviewer.tsx

Line 35 in 0388690

pdfjs.GlobalWorkerOptions.workerSrc = URL.createObjectURL(new Blob([pdfWorkerSource], {type: 'text/javascript'}));

Even with the correct import order, both worker builds would be included in the bundle, increasing its size.

This PR removes the default worker configuration and instead expects applications using this library to configure it, which is the same approach used by react-pdf. This makes it more reliable and easier to maintain (we will only need to update the worker once in E/App).

Related Issues

Expensify/App#76303

Manual Tests

1. Build with npm run build && npm pack.
2. Install it in the example app or E/App with npm install ../react-fast-pdf-1.0.31.tgz.
3. Open a PDF file.
4. Verify that the file is displayed properly.

Linked PRs

[QichenZhu]

Looks good overall.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

[QichenZhu]

@flodnv could you or someone on the team give this a second review? Thanks!

[flodnv]

@AndrewGable in @roryabraham's absence, could you please review this PR?

[os-botify]

🚀 Published to npm in 1.0.32 🎉

[flodnv]

Thank you @AndrewGable 🙇