It was broken after #65028

Report: https://s3.amazonaws.com/clickhouse-test-reports/0/ef34ec874a9e7e3cf1ac51a92a81ed46e5f1d1ed/stateless_tests__debug__s3_storage__%5B3_6%5D.html

The thing is this test uses 100 partitions so query does 200 S3 requests in total using multiple threads, and every thread uses 1MB buffers now. So now peek memory consumption of these two queries are ~400MB and ~500MB. More detailed diagnostics is here

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

This change was reverted

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

CI Settings (Only check the boxes if you know what you are doing):

• Allow: All Required Checks
• Allow: Stateless tests
• Allow: Stateful tests
• Allow: Integration Tests
• Allow: Performance tests
• Allow: All Builds
• Allow: batch 1, 2 for multi-batch jobs
• Allow: batch 3, 4, 5, 6 for multi-batch jobs

• Exclude: Style check
• Exclude: Fast test
• Exclude: All with ASAN
• Exclude: All with TSAN, MSAN, UBSAN, Coverage
• Exclude: All with aarch64, release, debug

• Do not test
• Woolen Wolfdog
• Upload binaries for special builds
• Disable merge-commit
• Disable CI cache

Closes #65472