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

[asfimport]

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 / @amousavigourabi

Related issues:

• Create specialized HadoopParquetWriter (is blocked by)
• Create specialized HadoopParquetReader (is blocked by)

_{Note: This issue was originally created as PARQUET-2381. Please see the migration documentation for further details.}