fix: handle binary content properly in WebDAV requests

[marcos-hairpieces]

Prevents corruption of binary files (images, videos, audio, PDFs) by passing streams through as-is instead of reading them as text for WebDAV content requests.

What?

This pull request fixes an issue where binary files (such as images, videos, audio, PDFs) served via WebDAV endpoints were being corrupted. The bug was caused by reading binary streams as text, which altered the file contents. The new logic detects binary content types and passes their streams through as-is, preventing corruption.

The regression was introduced in commit 20e1143e54c0ccfb2197c16b654ee5b098399ec9, which changed how streams were handled for WebDAV requests.

Tickets / Documentation

No existing tickets or documentation were found for this issue. The problem was identified and traced to the above commit.

Steps to Test

1. Add a binary file (e.g., test.png) to the WebDAV directory: /content/images/test.png.
2. Reference this image in your theme or access it directly perhaps via: /content/images/test.png in an img tag.
3. Before this fix, the image would be corrupted and not display correctly in the browser.
4. After this fix, the image should display correctly without corruption.

Screenshots (if appropriate)

1. How webdav images were being displayed before this change

2. How webdav images are being displayed after this change

cc @bigcommerce/storefront-team

[github-actions]

🎉 This PR is included in version 8.10.5 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 8.10.5

Your semantic-release bot 📦🚀