InternalParquetRecordReader Logging is Too Verbose

A low-level library like Parquet should be pretty quiet. It should just do its work and keep quiet. Most issues should be addressed by throwing Exceptions, and the occasional warning message otherwise it will clutter the logging for the top-level application. If debugging is required, administrator can enable it for the specific workload.

**Warning:** This is my opinion. No stats to back it up.

**Reporter**: [David Mollitor](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=belugabehr) / @belugabehr
**Assignee**: [David Mollitor](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=belugabehr) / @belugabehr
#### Related issues:
- [Lower Logging Level in ParquetOutputFormat](https://github.com/apache/parquet-java/issues/2436) (is related to)
#### PRs and other links:
- [GitHub Pull Request #742](https://github.com/apache/parquet-mr/pull/742)

_{**Note**: *This issue was originally created as [PARQUET-1758](https://issues.apache.org/jira/browse/PARQUET-1758). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*}

Start by reading the InternalParquetRecordReader logging paths and the linked Pull Request #742. Compare the current messages and levels with the issue's expectation that routine work stays quiet while exceptions and occasional warnings remain; done means the logging behavior matches that scope.

Written by the indexing model from the issue text.