Put dds (core of the script) elsewhere

[sebmestrallet]

The principle of nested, semantic data folders, and the script I developed to manage them, can be uncoupled from the application (hexahedal mesh generation). dds would be application-independent, and dds-hexmeshing would use dds under the hood.

3 inputs should be passed to dds:

• the path to paths.yml, the file listing where are dependencies
• the path to the data_folder_types/ folder, containing the definitions of data folder types
• the path to the algorithms/ folder, containing the definition of algorithms, which transform or create data folders of certain types

Then dds-hexmeshing will just contain paths.yml, data_folder_types/, algorithms/ and a main script instanciation and launching dds.