[api-minor] Use the ImageDecoder by default on Chrome

[calixteman]

The two mentioned bugs have been fixed a while back. So it should be fine to use this feature now.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.55%. Comparing base (2643125) to head (f578c7e).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #20961      +/-   ##
==========================================
+ Coverage   62.51%   62.55%   +0.04%     
==========================================
  Files         172      172              
  Lines      121789   121771      -18     
==========================================
+ Hits        76134    76179      +45     
+ Misses      45655    45592      -63     

Flag	Coverage Δ
fonttest	7.66% <ø> (?)
unittestcli	62.53% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Snuffleupagus]

The two mentioned bugs have been fixed a while back. So it should be fine to use this feature now.

Yes, but also kind of no :-)

https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support still lists Chrome 118 as supported, however the referenced bugs weren't fixed until somewhere around Chrome 132-133 (I think),
Most likely users on older Chrome versions will, sooner or later, report issues caused by these (since fixed) ImageDecoder bugs, and you'll then need to remember to check if their Chrome version is too old and point them to disable the option.

[Snuffleupagus]

r=me, assuming that you're OK with this potentially increasing the effort required when triaging issues.

[timvandermeij]

r=me, with passing tests. Thanks!

[Snuffleupagus]

Let's try to land this now since the minimum supported Chrome version was just updated to 125, which is much closer to the versions where those bugs are fixed (reducing the risk of issues reported here), in combination with the major PDF.js version number just being increased.