Stop using S3 Select in indexer

[sir-sigurd]

Description

TODO

• revert CI
• Changelog entry (skip if change is not significant to end users, e.g. docs only)

[codecov]

Codecov Report

Attention: Patch coverage is 36.11111% with 23 lines in your changes missing coverage. Please review.

Project coverage is 39.01%. Comparing base (6d70cc8) to head (18bee5a).
Report is 2 commits behind head on master.

Files with missing lines	Patch %	Lines
lambdas/indexer/index.py	32.35%	23 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4212      +/-   ##
==========================================
- Coverage   39.02%   39.01%   -0.02%     
==========================================
  Files         772      772              
  Lines       35540    35552      +12     
  Branches     5311     5111     -200     
==========================================
+ Hits        13870    13871       +1     
- Misses      20444    21074     +630     
+ Partials     1226      607     -619     

Flag	Coverage Δ
api-python	91.09% <ø> (ø)
catalog	14.30% <ø> (ø)
lambda	87.75% <36.11%> (-0.21%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

Copilot reviewed 4 out of 6 changed files in this pull request and generated no suggestions.

Files not reviewed (2)

• lambdas/indexer/pytest.ini: Language not supported
• lambdas/indexer/test-requirements.txt: Language not supported

Comments skipped due to low confidence (1)

lambdas/indexer/index.py:511

• [nitpick] The error message 'DuckDB select error' is vague. Consider providing more context or details in the error message.

logger_.error("DuckDB select error: %s", parsed["error"])

[nl0]

i don't see anything suspicious