fix: drop unused S3 logger middleware

[ferhatelmas]

What kind of change does this PR introduce?

Perf touch

What is the current behavior?

S3 logger isn't used so SDK uses no op logger which discards output line but it still runs a filter for sensitive data.

What is the new behavior?

No need to pay the price, disable it completely.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coveralls]

Coverage Report for CI Build 29824646150

Coverage increased (+0.002%) to 79.591%

Details

• Coverage increased (+0.002%) from the base build.
• Patch coverage: 9 of 9 lines across 3 files are fully covered (100%).
• 1 coverage regression across 1 file.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

1 previously-covered line in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
src/http/routes/s3/index.ts	1	82.99%

---

Coverage Stats

Relevant Lines:	12764
Covered Lines:	10607
Line Coverage:	83.1%
Relevant Branches:	7448
Covered Branches:	5480
Branch Coverage:	73.58%
Branches in Coverage %:	Yes
Coverage Strength:	426.41 hits per line

---

💛 - Coveralls

[claude]

Beyond the flagged S3Store internal client gap, I checked the other two S3 client construction paths in this diff (S3Backend.createS3Client for the default and private-asset clients, and the shared S3Locker client in tus/index.ts) — both correctly call middlewareStack.remove('loggerMiddleware') right after construction, and the new adapter.test.ts case asserts this for both S3Backend clients. No other S3Client instantiations exist in the diff.

Extended reasoning...

Small, low-risk perf-only change (removes a middleware entry from AWS SDK clients); no security or correctness concerns beyond the inline nit already noted.