ci: [experiment] force torch >=2.13 to confirm CI hang

[bhimrazy]

What does this PR do?

Control experiment (do not merge). Forces torch >=2.13 to confirm it causes the processing-test CI hang. Pairs with #841 (torch <2.13, expected green).

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73%. Comparing base (5201360) to head (cd2d00a).
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

❗ There is a different number of reports uploaded between BASE (5201360) and HEAD (cd2d00a). Click for more details.

HEAD has 30 uploads less than BASE

Flag	BASE (5201360)	HEAD (cd2d00a)
unittests	13	3
3.10	3	1
3.11	3	1
3.12	3	1
3.13	2	0
macos-14	5	0
ubuntu-22.04	5	0
3.14	2	0

Additional details and impacted files

@@         Coverage Diff          @@
##           main   #842    +/-   ##
====================================
- Coverage    81%    73%    -7%     
====================================
  Files        54     54            
  Lines      7671   7671            
====================================
- Hits       6186   5612   -574     
- Misses     1485   2059   +574     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[bhimrazy]

Closing this experiment — we ruled out torch as the cause of the CI failures. Root cause is pyarrow 25.0.0, which segfaults during parquet indexing (16 failing tests in tests/streaming/test_parquet.py). The real fix is in #841, which now pins pyarrow <25 instead.