Avoid re-calculating the `xScaleBlockOffset` when not necessary in `JpegImage._getLinearizedBlockData`
Avoid re-calculating the `xScaleBlockOffset` when not necessary in `JpegImage._getLinearizedBlockData`

As can be seen in the code, the `xScaleBlockOffset` typed array doesn't depend on the actual image data but only on the width and x-scale. The width is obviously consistent for an image, and it turns out that in practice the `componentScaleX` is quite often identical between two (or more) adjacent image components.
All-in-all it's thus not necessary to *unconditionally* re-compute the `xScaleBlockOffset` when getting the JPEG image data.

While avoiding, in many cases, one or more loops can never be a bad thing these changes are unfortunately completely dominated by the rest of the JpegImage code and consequently doesn't really show up in benchmark results. *Hence I'd understand if this patch is ultimately deemed not necessary.*

macroplant/pdf.js,macroplant/pdf.js,mozilla/pdf.js,nawawi/pdf.js,nawawi/pdf.js,xavier114fch/pdf.js,Snuffleupagus/pdf.js,Snuffleupagus/pdf.js,Shoobx/pdf.js,showpad/mozilla-pdf.js,caremerge/pdf.js,Shoobx/pdf.js,mozilla/pdf.js,Snuffleupagus/pdf.js,macroplant/pdf.js,showpad/mozilla-pdf.js,nawawi/pdf.js,showpad/mozilla-pdf.js,timvandermeij/pdf.js,timvandermeij/pdf.js,mozilla/pdf.js,timvandermeij/pdf.js,Shoobx/pdf.js,caremerge/pdf.js,xavier114fch/pdf.js