[MB-8798] Fix deprecation warning for pdf files in the document viewer progress callback

[duncan-truss]

Description

This PR updates our document viewer library react-file-viewer fork to use changes to no longer use the deprecated getDocument function with the progress loading callback trussworks/react-file-viewer#5. This only applies the loading of PDF files in the orders or payment requests document viewer so make sure you are looking at uploads that are not images.

When that PR gets merged into master I will update the package.json to no longer resolve to using the branch name.

It looks like we're still seeing another warning about an undefined function but we will need to upgrade pdf.js to eventually get rid of this mozilla/pdf.js#3768

Reviewer Notes

Is there anything you would like reviewers to give additional scrutiny?

Setup

Add any steps or code to run in this section to help others prepare to run your code:

make db_dev_e2e_populate
make server_run
make office_client_run

1. Login as a TOO user
2. Find the move from the queue with locator AMDORD http://officelocal:3000/moves/AMDORD/orders
3. Navigate to the Edit Orders page if you have not gone there directly
4. Open the devtools browser console option + command + i or from the Tools -> Browser Tools -> Web Developer Tools menu in Firefox.
5. Verify there is no more deprecation warning logged to the console when the small.pdf document is loaded.

Code Review Verification Steps

• If the change is risky, it has been tested in experimental before merging.
• Code follows the guidelines for Logging
• The requirements listed in Querying the Database Safely have been satisfied.
• Any new migrations/schema changes:
  • Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
  • Have been communicated to #g-database
  • Secure migrations have been tested following the instructions in our docs
• There are no aXe warnings for UI.
• This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
• Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
• User facing changes have been reviewed by design.
• Request review from a member of a different team.
• Have the Jira acceptance criteria been met for this change?

References

• Jira story for this change

Screenshots

[robot-mymove]

	Messages
📖	🔗 MB-8798

Generated by 🚫 dangerJS against 8a310fa

[github-actions]

Bundle difference

Old size	New size	Diff
46.77 MB	46.77 MB	0 B (0.00%)

[monfresh]

Works as described. Thanks!

[github-actions]

Bundle difference

Old size	New size	Diff
46.78 MB	46.78 MB	0 B (0.00%)

[github-actions]

Bundle difference

Old size	New size	Diff
46.78 MB	46.78 MB	0 B (0.00%)

[github-actions]

Bundle difference

Old size	New size	Diff
46.78 MB	46.78 MB	0 B (0.00%)