DW-23: Fixing System.OutOfMemoryException in x86

[mee-ironsoftware]

Description

The root cause of the issue lies in the ExportBytes() function when attempting to return a large byte array containing a giant image (4958x7016 pixels). This high resolution consumes significant memory, leading to an OutOfMemoryException.

Fixing only SaveAs() function by change to use FileStream instead of byte[].

Doesn't have a good solution for ExportBytes() because we export a byte array out. To solve this issue on x86 please change to use ExportStream() instead.

Fixes #DW-23

Type of change

Please select the relevant option by placing an 'x' inside the brackets, like this: [x].

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🏗️ Internal/structural update (non-breaking change that improves code quality, organization, or performance)
• 📚 This change requires a documentation update
• 🚀 DevOps build chain modification for release
• 🤖 DevOps build chain modification for CI

How Has This Been Tested?

Test locally using x86 and add x86 tests on DevOps (.NET472, .NET60, and .NET70)

Checklist:

Please run through the checklist as much as possible and mark the items completed by placing an 'x' inside the brackets, like this: [x].

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have successfully run all unit tests on Windows
• I have successfully run all unit tests on Linux

[first-ironsoftware]

LGTM 🎉