fix(/context): gracefully handle huge context files + ux

[GoodluckH]

#1254

demo-context-file-exceeded-limit.mp4

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 16.75%. Comparing base (dd6ca31) to head (b1ac450).
⚠️ Report is 416 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1331   +/-   ##
=======================================
  Coverage   16.75%   16.75%           
=======================================
  Files         213      213           
  Lines       20704    20704           
  Branches      871      871           
=======================================
  Hits         3468     3468           
  Misses      17236    17236           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[brandonskiser]

also a note - from checking process_path it seems like it's never invoked with force == true so it would be nice to just remove that altogether

[brandonskiser]

Also a major TODO here is to limit the total size of files loaded. This whole context loading logic loads everything into memory before dropping, so it's super trivial to just run into OOM with a glob that matches a ton of large files.

[brandonskiser]

An API that doesn't require copying potentially very large files would also be nice, just for memory performance (not like it matters even)

I would rather this func maybe take an iterator over files, and return a vec of dropped file names instead. Then, your files could be e.g. a HashMap of file name to file content