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.*}

Comienza con la documentación de migración enlazada en la issue y, después, lee las issues especializadas relacionadas con HadoopParquetWriter y HadoopParquetReader. Identifica los métodos principales de lectura/escritura que dependen de clases de Hadoop y las interfaces genéricas de Parquet disponibles. Se considera terminado cuando esos métodos estén deprecated o desacoplados según lo descrito, con la ruta específica de Hadoop aislada sin imponer la dependencia a los usuarios del core.

Escrito por el modelo de indexación a partir del texto del issue.