Deprecate methods relying on Hadoop classes when alternatives using more generic Parquet interfaces are available

Deprecate methods relying on Hadoop classes when alternatives using Parquet interfaces are available. This would allow for fully decoupling from Hadoop for simple read/write (and potentially rewrite) operations in the future, where we are now only on track to decouple from hadoop-client-runtime in the near future.

We could decide to still keep Hadoop methods available through convenience classes in their own Hadooped module, but for core read/write logic to be available without forcing users into the Hadoop dependency, we will need to fully strip the core readers and writers of these references.

**Reporter**: [Atour Mousavi Gourabi](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=amousavigourabi) / @amousavigourabi
#### Related issues:
- [Create specialized HadoopParquetWriter](https://github.com/apache/parquet-java/issues/2854) (is blocked by)
- [Create specialized HadoopParquetReader](https://github.com/apache/parquet-java/issues/2855) (is blocked by)

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

先从 issue 中链接的迁移文档开始，然后阅读与 HadoopParquetWriter 和 HadoopParquetReader 相关的专门 issue。识别依赖 Hadoop 类的核心读写方法，以及可用的通用 Parquet 接口。完成的标准是：这些方法已按描述标记为 deprecated 或完成解耦，并且 Hadoop 专用路径已隔离，不会强迫 core 用户引入该依赖。

由索引模型根据 Issue 内容生成。