fix: use original accept encoding header to resolve s3 request signing issue

[itslenny]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

S3 calls that include an accept-encoding header fail to be verified because Cloudflare modifies this header. This impacts those using the Go SDK V2 (and potentially others)

What is the new behavior?

Replace the (cloudflare modified) accept-encoding header with the value of x-original-accept-encoding so the request can be verified successfully.

Additional context

• Fixes AWS Go SDK V2 Incompatibility: SignatureDoesNotMatch Error When Using LiveKit Egress with Supabase Storage #646
• Fixes Golang aws sdk v2 cannot upload to supabase storage #577
• Depends on corresponding api gateway update to provide this new header value

[coveralls]

Pull Request Test Coverage Report for Build 16301044024

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 4 of 9 (44.44%) changed or added relevant lines in 1 file are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.03%) to 76.924%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/storage/protocols/s3/signature-v4.ts	4	9	44.44%

Files with Coverage Reduction	New Missed Lines	%
src/internal/database/tenant.ts	2	83.25%

Totals
Change from base Build 16264541738:	-0.03%
Covered Lines:	20440
Relevant Lines:	26341

---

💛 - Coveralls