[ENH]: replace .get_* methods on blockfile API with .get_range()

[codetheweb]

Description of changes

Last PR in this stack. Propagates .get_range() API to the rest of the codebase.

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

n/a

[codetheweb]

• [ENH]: make get_range() a lazy Stream #3009
• [ENH]: replace .get_* methods on blockfile API with .get_range() #2936 👈
• [ENH]: replace get_* methods on memory blockfile impl with get_range() #2935
• [ENH]: replace get_* methods on Arrow blocks with get_range() #2934
• [ENH]: replace get_block_ids_* with get_block_ids_range() in SparseIndex #2921
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @codetheweb and the rest of your teammates on Graphite

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[codetheweb]

Merge activity

• Nov 4, 1:28 PM EST: A user started a stack merge that includes this pull request via Graphite.
• Nov 4, 1:38 PM EST: Graphite rebased this pull request as part of a merge.
• Nov 4, 1:39 PM EST: A user merged this pull request with Graphite.