[Feature Request] Preserve original image file type and size during upload

[dkmtech32]

Current Behavior
When uploading images to Payload CMS with S3 storage, Sharp automatically processes and compresses the images, even for the "original" version. This results in:

• Reduced file size
• Potential format conversion
• Loss of original image quality
• Modified metadata

Desired Behavior
Need a way to store the original image file exactly as uploaded, maintaining:

• Original file size
• Original file format/type
• Original quality
• Original metadata
• While still allowing additional image sizes to be generated

Use Case
This is crucial for:

• Photography websites requiring exact original files
• Digital asset management systems
• Professional image archives
• Situations where image fidelity is critical

Current Workarounds Attempted

1. Setting formatOptions: null in imageSizes
2. Using withoutReduction: true
3. Configuring Sharp options with maximum quality
4. Custom upload handlers

None of these completely solve the issue as Sharp still processes the image at the initial upload stage.

Proposed Solution
Would it be possible to:

1. Add a flag to bypass Sharp processing for original files?
2. Or provide a configuration option to store raw files?
3. Or implement a direct upload path for originals?

Environment

• Payload CMS version: [version]
• Storage: @payloadcms/storage-s3
• Database: MongoDB
• Node.js version: [version]

Additional Context
This feature would be particularly valuable for professional photography and digital asset management use cases where maintaining the exact original file is crucial.

Would love to hear thoughts on the best approach to implement this while maintaining Payload's excellent image handling capabilities for derived sizes.