feat(gatsby-plugin-sharp): Use file streams instead of file paths

[LekoArts]

Description

Converts sharp usage based on file paths to file streams, e.g.

// Before
const imgStats = await sharp(file.absolutePath).stats()

// After
const pipeline = sharp()
fs.createReadStream(file.absolutePath).pipe(pipeline)
const imgStats = await pipeline.stats()

For the writing of files we use sharpPipeline.toBuffer() + fs.writeFile() for now. We probably will change it to filestream in future PR (will just need to revert 31cfaf3).

Running the image-processing benchmark didn't show any major speed improvement/degradation

Related Issues

[ch37488]

[KyleAMathews]

Nice! Might reduce memory usage perhaps depending on how Sharp does things

[wardpeet]

@LekoArts & @pieh by making queueImageResizing and others async, doesn't this break the contract with plugins like gatsby-plugin-sqip? Should we go to a git patch instead to not break this in master?

[LekoArts]

Good point, we also use the function in gatsby-transformer-sharp. If we want to keep the behavior then we need to do git patch / adjust more

[pieh]

I reverted async change to queueImageResizing from this PR - breaking contract with it is valid reason to do so. I still think overall it would be beneficial for it to be async, but it doesn't really belong in this PR. Potential way to move forward with it (in another PR) would be introducing queueImageResizingAsync variant, updating plugins we maintatin to use and keeping old sync one (and deprecating that one) to not cause too much problems for 3rd party plugins that might rely on it today.

[wardpeet]

LGTM!