87 add functionality to use input iterator in rail for parquet files

[joselotl]

Problem & Solution Description (including issue #)

Code Quality

• My code follows the code style of this project
• I have written unit tests or justified all instances of #pragma: no cover; in the case of a bugfix, a new test that breaks as a result of the bug has been added
• My code contains relevant comments and necessary documentation for future maintainers; the change is reflected in applicable demos/tutorials (with output cleared!) and added/updated docstrings use the NumPy docstring format
• Any breaking changes, described above, are accompanied by backwards compatibility and deprecation warnings

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (f5fcae2) 100.00% compared to head (4076457) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #88   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines          658       673   +15     
=========================================
+ Hits           658       673   +15     

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

[joselotl]

I added some functions to solve bug report LSSTDESC/rail#116 as well as LSSTDESC/rail_bpz#42

I don't know why it is reporting a change in coverage, I added the apropiate tests to the new functions

[eacharles]

There were two test functions with the same name. Also added a test for an unsupported file type, should be at 100% coverage now.

[eacharles]

Looks good, fixed a name collision in tests.