Restructure Html2Parquet with its own dpk_ namespace

[touma-I]

Why are these changes needed?

This is a first of a series of restructuring changes that are done to have each transform built as its own module (e.g. dpk_html2parquet) with a ray submodule (dpk_html2parquet.ray ).

• Removed python and ray folders and keep Dockerfile.python and Dockerfile.ray
• remove pyproject.toml
• move python code under dpk_html2parquet
• move ray code under dpk_html2parquet/ray
• change import statement to include module name
• replace recursive Makefile and use targets from .make.cicd.targets
• adapt kfp_ray/Makefile and other make target

Related issue number (if any).

https://github.com/IBM/data-prep-kit/issues/774

[roytman]

if each transformer builds its own module, should we add init.py files and create a unified namespace? For example: instead from dpk_html2parquet.transform import Html2ParquetTransformConfiguration use from dpk_html2parquet import Html2ParquetTransformConfiguration

the same for the ray runtime.

[touma-I]

If we are doing so massive refactoring, should we combine test and test-data into one dir, e.g.

• test

  • data

  • input

  • expected

@roytman Why not leave it to the transform owner developer to decide if they want to nest the test-data under test. All we care about that we have a test folder for running the pytest. no ? where the developer puts their data is up to them. no ?

[touma-I]

if each transformer builds its own module, should we add init.py files and create a unified namespace? For example: instead from dpk_html2parquet.transform import Html2ParquetTransformConfiguration use from dpk_html2parquet import Html2ParquetTransformConfiguration

the same for the ray runtime.

How did I miss that? Done. Thanks @roytman