Make bounds configurable in csv ReaderBuilder

[gsserge]

Which issue does this PR close?

Closes #1327.

Rationale for this change

ReaderBuilder for cvs has the bounds field, which currently cannot be set by a user.

What changes are included in this PR?

This PR adds a new public method ReaderBuilder::with_bounds(), and changes ReaderBuilder::build() to correctly pass the configured bounds to Reader::from_csv_reader().

Are there any user-facing changes?

Users can now configure bounds when using ReaderBuilder.

[codecov-commenter]

Codecov Report

Merging #1341 (b896496) into master (ecba7dc) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1341      +/-   ##
==========================================
- Coverage   83.04%   83.03%   -0.01%     
==========================================
  Files         181      181              
  Lines       52937    52948      +11     
==========================================
+ Hits        43960    43968       +8     
- Misses       8977     8980       +3     

Impacted Files	Coverage Δ
arrow/src/csv/reader.rs	88.25% <100.00%> (+0.13%)	⬆️
parquet_derive/src/parquet_field.rs	65.98% <0.00%> (-0.46%)	⬇️
arrow/src/array/transform/mod.rs	84.39% <0.00%> (-0.14%)	⬇️

---

Continue to review full report at Codecov.

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

[gsserge]

It might be better from the API perspective for the with_bounds() method to have explicit start and end parameters instead of wrapping a tuple in Some: .with_bounds(0, 2) instead of .with_bounds(Some((0, 2))).

[nevi-me]

It might be better from the API perspective for the with_bounds() method to have explicit start and end parameters instead of wrapping a tuple in Some: .with_bounds(0, 2) instead of .with_bounds(Some((0, 2))).

I think either approach is fine, we would often pass an Option in case one wants to reset an optional value. in practise though, I don't know whether a readerbuilder can be reused, as it could be cheap to create a new one with different configs.

I'll merge this one for now, and then if you'd like to update to exclude the Option, we can do that before the next major release to avoid breaking changes.

[alamb]

Nice ❤️