refactor: drop version_engine

[project-defiant]

✨ Context

Due to the fact that the version engine that was a concept implemented to fit the datasource version inference directly from provided input parameters and use it as a (dataset triggerer in the airflow orchestration airflow datasets triggers this is no longer in the scope of the gentropy.

Moreover the version reasoning caused more trouble, this is why I decided to remove it from here.

🛠 What does this PR implement

This PR drops the version_engine from the gentropy.

🙈 Missing

The version engine is still valid, it has to be moved to the orchestration and can then trigger the dataset version infernence.

🚦 Before submitting

• Do these changes cover one single feature (one change at a time)?
• Did you read the contributor guideline?
• Did you make sure to update the documentation with your changes?
• Did you make sure there is no commented out code in this PR?
• Did you follow conventional commits standards in PR title and commit messages?
• Did you make sure the branch is up-to-date with the dev branch?
• Did you write any new necessary tests?
• Did you make sure the changes pass local tests (make test)?
• Did you make sure the changes pass pre-commit rules (e.g poetry run pre-commit run --all-files)?

[project-defiant]

@DSuveges hopefully this will simplify a bit.

[DSuveges]

Logic and references were removed to handle datasource versions. As as consequence, the version information in pre-preprocessed input datasets will no longer available (unless explicitly coded in the configuration paths.).