feat: add more v1 methods to v2 client

[sirewix]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 4.00%. Comparing base (221f1f7) to head (4fd53b5).
Report is 2 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff            @@
##            main     #55      +/-   ##
========================================
+ Coverage   3.19%   4.00%   +0.80%     
========================================
  Files        857     856       -1     
  Lines      36616   36535      -81     
========================================
+ Hits        1171    1462     +291     
+ Misses     35445   35073     -372     

see 31 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 221f1f7...4fd53b5. Read the comment docs.

[tlater-famedly]

Nice, but I'm not a big fan of sneaking in a bunch of refactoring with a feature commit.

I avoid being too precise with this because it can be a ton of work for more hairy commits, but in this case it should be really trivial. Can we split this into two commits, one with the refactor and another with the new method?

[sirewix]

I agree, initially I added the support for org id in headers, which required changing all the lines where PaginationHandler was used, so I decided it was a good chance to add one type parameter. And then I rebased my branch and turned out the org id feature was added already

[tlater-famedly]

We should try to add proper sorting to these methods upstream.

[tlater-famedly]

Love the unboxing of the PaginationHandler, thanks for taking your time to do that.

[tlater-famedly]

Ready to go except for one detail that almost slipped by me?